security-scanner
Skill4 starsChanged 5 months agoMITView on GitHub
Scan code and dependencies for security vulnerabilities. Check npm audit, pip safety, and common security issues.
- Reads credentials
- Installs packages
14 other projects use a version of this.
Adopted by
Most recently taken up by
- rmichak/claude-skillstheir own version, first seen Nov 8, 2026
- zedarvates/frugal-skillstheir own version, first seen Nov 8, 2026
- kcayme/k-agentstheir own version, first seen Nov 1, 2026
- jazzpujols34/claude-skillstheir own version, first seen Oct 13, 2026
- leonvanzyl/agentic-coding-starter-kittheir own version, first seen Oct 8, 2026
- alexblag023/claude-skillstheir own version, first seen Oct 1, 2026
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- leonvanzyl/agentic-coding-starter-kit★ 447same name
- glincker/claude-code-marketplace★ 37same name
- dkpapadopoulos/auto-claude-skills★ 6same name
- casedone/claude-code-security-plugins★ 4same name
- leonvanzyl/claude-code-pro-workflow-demo★ 4same name
- mehdiozdemir/awesome-agent-skills★ 2same name
- alexblag023/claude-skills★ 1same name
- cicoccc/openclaw-security-scanner★ 1same name
- rmichak/claude-skills★ 1same name
- zedarvates/frugal-skills★ 1same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- bet-journalSkill
- clv-journalSkill
- crypto-priceSkill
- data-vizSkill
- devin-integrationSkill
- dfs-optimizerSkill
- git-helperSkill
- judge-auditSkill
- kelly-criterionSkill
- market-sentimentSkill
- nft-trackerSkill
- portfolio-rebalancerSkill
- screenshot-annotatorSkill
- sports-oddsSkill
- streak-trackerSkill
- weather-forecastSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 40
Check for known vulnerabilities in npm packages:
- Distinctive: line 60
Check Python dependencies with pip-audit:
- Distinctive: line 82
Search for potential API keys and secrets:
- Distinctive: line 90
Check for potentially dangerous code patterns:
- Distinctive: line 121
Ensure sensitive files are ignored:
- Distinctive: line 149
Run a quick audit on a project:
- Very specific: line 183
Create SECURITY.md in your repo to establish responsible disclosure guidelines.
- Distinctive: line 195
Run security scans in CI/CD pipelines
- Distinctive: line 197
Use pre-commit hooks to catch secrets before commit
- Distinctive: line 199
Keep dependencies updated regularly
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Security Scanner
Scan your projects for security vulnerabilities in dependencies and common code issues.
Dependency Scanning
NPM Projects
Check for known vulnerabilities in npm packages:
npm auditGet JSON output for parsing:
npm audit --json | jq '{vulnerabilities: .metadata.vulnerabilities, total: .metadata.vulnerabilities.total}'Fix automatically where possible:
npm audit fixPython Projects
Check Python dependencies with pip-audit:
pip install pip-audit && pip-auditOr use safety (requires free API key from https://safetycli.com/):
pip install safety && safety checkCheck requirements.txt directly:
pip-audit -r requirements.txtCode Security Checks
Find Hardcoded Secrets
Search for potential API keys and secrets:
grep -rn "api_key\|apikey\|secret\|password\|token" --include="*.js" --include="*.ts" --include="*.py" --include="*.env" .Find Dangerous Functions
Check for potentially dangerous code patterns:
# JavaScript/TypeScript - eval usage
grep -rn "eval(" --include="*.js" --include="*.ts" .
# Python - exec/eval usage
grep -rn "exec(\|eval(" --include="*.py" .
# SQL injection risks
grep -rn "execute.*%s\|execute.*f\"" --include="*.py" .Check for Debug Code
Find debug statements that shouldn't be in production:
grep -rn "console.log\|debugger\|print(" --include="*.js" --include="*.ts" --include="*.py" .Environment Security
Check for Exposed .env Files
find . -name ".env*" -not -path "*/node_modules/*" -not -path "*/.git/*"Verify .gitignore
Ensure sensitive files are ignored:
cat .gitignore | grep -E "\.env|secret|credential|\.pem|\.key"Docker Security
Scan Docker Images
Using Trivy (install: https://trivy.dev/):
trivy image your-image:tagCheck Dockerfile Best Practices
# Check for root user
grep -n "USER root" Dockerfile
# Check for latest tag
grep -n "FROM.*:latest" DockerfileQuick Security Audit
Run a quick audit on a project:
# For npm projects
echo "=== NPM Audit ===" && npm audit 2>/dev/null || echo "Not an npm project"
# Check for secrets
echo "=== Potential Secrets ===" && grep -rn "password\|secret\|api_key" --include="*.js" --include="*.py" --include="*.ts" . 2>/dev/null | head -20
# Check for .env files
echo "=== Environment Files ===" && find . -name ".env*" -not -path "*/node_modules/*" 2>/dev/nullGitHub Security Features
Enable Dependabot
Create .github/dependabot.yml:
version: 2
updates:
- package-ecosystem: "npm"
directory: "/"
schedule:
interval: "weekly"
- package-ecosystem: "pip"
directory: "/"
schedule:
interval: "weekly"Security Policy Template
Create SECURITY.md in your repo to establish responsible disclosure guidelines.
Resources
Tips
- Run security scans in CI/CD pipelines
- Set up Dependabot for automatic dependency updates
- Use pre-commit hooks to catch secrets before commit
- Review third-party dependencies before adding them
- Keep dependencies updated regularly
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

