security-scanning-security-sast — Claude Code skill
security-scanning-security-sast — a skill for static code analysis (SAST) that detects vulnerabilities, hardcoded secrets, and security policy violations across multiple languages and frameworks.
MIT ★ 50,109 updated 2026-10-29
npx skills add sickn33/agentic-awesome-skills --skill security-scanning-security-sast -a claude-codeWhat security-scanning-security-sast does
The skill scans source code for injection flaws, leaked credentials, unsafe framework patterns, and custom policy violations. For focused credential scanning, OWASP Top 10 mapping, and REST/GraphQL endpoint checks, use the dedicated utilities security-secrets.md, security-owasp.md, security-api.md.
Key limitation: the skill analyzes source code and build artifacts only; it does not replace runtime testing or penetration testing. It requires code access and is blocked in environments where third-party scanning tools are prohibited. Before enabling auto-fixes or release blocking, obtain expert review — do not upload proprietary code to external services without approval.
What it helps with
- detect injection flaws and hardcoded secrets before deployment
- verify code meets OWASP Top 10 and PCI-DSS requirements
- assess legacy applications for security vulnerabilities
- enforce custom security policies across the codebase
- automate security checks in CI/CD before PR merge
Example prompts for the agent
- Scan this project for SAST vulnerabilities before deploying to production
- Check the code for hardcoded API keys and credentials
- Analyze this framework for OWASP Top 10 compliance
How to install security-scanning-security-sast
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill security-scanning-security-sast -a claude-code2Manually: put the files in place
~/.claude/skills/security-scanning-security-sast/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/security-scanning-security-sast/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill security-scanning-security-sast -a codex2Manually: put the files in place
.agents/skills/security-scanning-security-sast/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill security-scanning-security-sast -a cursor2Manually: put the files in place
.cursor/skills/security-scanning-security-sast/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sickn33/agentic-awesome-skills skills/security-scanning-security-sast2Manually: put the files in place
.github/skills/security-scanning-security-sast/SKILL.md1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill security-scanning-security-sast -a gemini-cli2Platform CLI
gemini skills install https://github.com/sickn33/agentic-awesome-skills --path skills/security-scanning-security-sastManually: put the files in place
.devin/skills/security-scanning-security-sast/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill security-scanning-security-sast -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about security-scanning-security-sast
How do I install security-scanning-security-sast in Claude Code?
Run npx skills add sickn33/agentic-awesome-skills --skill security-scanning-security-sast -a claude-code, then open ~/.claude/skills/security-scanning-security-sast/SKILL.md to configure it.
What does the security-scanning-security-sast skill do?
It scans source code for vulnerabilities: injection flaws, credential leaks, unsafe patterns, and custom policy violations. Supports many languages and frameworks, helps comply with OWASP, PCI-DSS, and SOC2.
When should I not use this skill?
If you need runtime testing or penetration testing, use specialized tools instead. The skill requires source code access and is not available in environments where third-party scanners are prohibited.
Source text
SKILL.md · MIT
--- name: security-scanning-security-sast description: 'Static Application Security Testing (SAST) for code vulnerability analysis across multiple languages and frameworks ' risk: critical source: community date_added: '2026-02-27' --- # SAST Security Plugin Static Application Security Testing (SAST) for comprehensive code vulnerability detection across multiple languages, frameworks, and security patterns. ## Detailed Guide Read [the detailed guide](references/detailed-guide.md) before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely. ## Use this skill when Use for code review security analysis, injection vulnerabilities, hardcoded secrets, framework-specific patterns, custom security policy enforcement, pre-deployment validation, legacy code assessment, and compliance (OWASP, PCI-DSS, SOC2). **Specialized tools**: Use `security-secrets.md` for advanced credential scanning, `security-owasp.md` for Top 10 mapping, `security-api.md` for REST/GraphQL endpoints. ## Do not use this skill when - You only need runtime testing or penetration testing - You cannot access the source code or build outputs - The environment forbids third-party scanning tools ## Safety - Avoid uploading proprietary code to external services without approval. - Require review before enabling auto-fix or blocking releases. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
© sickn33 · MIT · sickn33/agentic-awesome-skills