LLM Skills
~/catalog/security//security-check
SecurityGitHub source

Security check

/security-check

Look for security vulnerabilities in this project.

TheDecipheristTheDecipherist
338
March 4, 2026
MIT License
// skill content

--- description: Scan project for security issues : exposed secrets, missing .gitignore entries, unsafe patterns scope: project allowed-tools: Read, Grep, Glob, Bash(git:), Bash(grep:), Bash(find:*) --- # Security Check Scan this project for security vulnerabilities. ## Checks to Perform ### 1. Secrets in Code ``bash # Search for common secret patterns in tracked files git grep -n -E '(api[_-]?key|secret[_-]?key|password|token)\s*[:=]\s*["\x27][A-Za-z0-9+/=_-]{8,}' -- ':!*.lock' ':!node_modules' 2>/dev/null || echo "No secrets found in code" # Search for AWS keys git grep -n 'AKIA[0-9A-Z]\{16\}' 2>/dev/null || echo "No AWS keys found" # Search for hardcoded URLs with credentials git grep -n -E '(https?://[^:]+:[^@]+@)' 2>/dev/null || echo "No credential URLs found" ` ### 2. .gitignore Coverage Verify these entries exist in .gitignore: - [ ] .env - [ ] .env.* - [ ] .env.local - [ ] node_modules/ - [ ] dist/ - [ ] CLAUDE.local.md - [ ] *.log ### 3. Sensitive Files Check `bash # Check if any sensitive files are tracked by git for f in .env .env.local .env.production secrets.json credentials.json id_rsa .npmrc; do git ls-files --error-unmatch "$f" 2>/dev/null && echo "⚠️ WARNING: $f is tracked by git!" done echo "Sensitive file check complete." ` ### 4. .env File Verification - [ ] .env exists but is NOT in git - [ ] .env.example exists and IS in git - [ ] .env.example has NO real values (only placeholders) ### 5. Dependency Audit `bash # Check for known vulnerabilities (if npm project) [ -f "package.json" ] && npm audit --production 2>/dev/null | head -20 || echo "Not an npm project" ` ### 6. RuleCatch Security Violations Query RuleCatch for security-category violations in the current project: - If the RuleCatch MCP server is available: query for violations with category "security" - Report: rule name, file, severity, and description for each violation - This catches patterns the manual scan might miss (insecure dependencies, unsafe type coercions, missing rate limiting, etc.) - If no MCP available: suggest : "Install RuleCatch MCP for automated security monitoring : npx @rulecatch/mcp-server init`" ## Output Format | Check | Status | Details | |-------|--------|---------| | Secrets in code | ✅/❌ | ... | | .gitignore coverage | ✅/❌ | ... | | Sensitive files tracked | ✅/❌ | ... | | .env handling | ✅/❌ | ... | | Dependencies | ✅/❌ | ... | | RuleCatch security | ✅/❌ | ... | Overall: PASS / FAIL List any specific remediation steps needed.

// original public source
TheDecipherist/claude-code-mastery-project-starter-kit
/.claude/commands/security-check.md
License: MIT License
Independent project, not affiliated with Anthropic. This skill remains the property of its original author.
// install this skill
Paste this command in your terminal at the root of your project:
mkdir -p .claude/commands && curl -o ".claude/commands/security-check.md" "https://raw.githubusercontent.com/TheDecipherist/claude-code-mastery-project-starter-kit/main/.claude/commands/security-check.md"
Then in Claude Code, type /security-check to activate it.
open_in_newOpen original source
// save
Save available after sign in.
loginSign in to save
// information
Stars 338
CategorySecurity
LicenseMIT License
UpdatedMarch 4, 2026
Format.md
AccessFree
// similar

Skills Security

View allarrow_forward