security-check

security-check is a command for Claude Code from dachivadachkoria/claude-code-starter-kit. It costs 11 tokens per session (1,021 once invoked), scanned A, original, MIT.

A security-audit command that checks project code and dependencies for known weaknesses and unsafe patterns. It also looks for exposed secrets such as passwords or API keys.

In plain words
What is it for?
Use it on Python, JavaScript or TypeScript, and Go projects to review dependencies, source code, authentication, input handling, logging, and secret exposure.
Why use it?
It helps identify vulnerable packages, injection risks, missing security checks, unsafe settings, and accidentally committed secrets.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/dachivadachkoria/claude-code-starter-kit/security-check
Clone the repo
git clone --depth 1 https://github.com/dachivadachkoria/claude-code-starter-kit

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for security-check

README.md
[![agentmods](https://agentmods.dev/badge/commands/dachivadachkoria/claude-code-starter-kit/security-check.svg)](https://agentmods.dev/commands/dachivadachkoria/claude-code-starter-kit/security-check)
Your own site
<a href="https://agentmods.dev/commands/dachivadachkoria/claude-code-starter-kit/security-check"><img src="https://agentmods.dev/badge/commands/dachivadachkoria/claude-code-starter-kit/security-check.svg" alt="Measured on agentmods" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,021 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.01021
Opus 5 $0.00005 $0.00511
Sonnet 5 $0.00002 $0.00204
Haiku 4.5 $0.00001 $0.00102

Measured 4d ago against content hash cb7ddf453e22, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

security-check scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

- Command injection (os.system, exec, eval)
.claude/commands/security-check.md · 150 lines

How it starts

The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Security Vulnerability Scanner

Perform security audit on: $ARGUMENTS (default: entire project)

Scan Categories

1. Dependency Vulnerabilities

Python:

pip-audit --desc 2>/dev/null || pip install pip-audit && pip-audit --desc
safety check 2>/dev/null || true

JavaScript:

npm audit --json
npx audit-ci --moderate

Go:

govulncheck ./...

2. Code Security Issues

Scan for these patterns:

🔴 Critical

  • Hardcoded secrets/API keys
  • SQL injection vulnerabilities
  • Command injection (os.system, exec, eval)
  • Path traversal (../ in file operations)
  • Insecure deserialization
  • XXE vulnerabilities

🟠 High

  • Missing input validation
  • Insecure cryptography (MD5, SHA1 for passwords)
  • Sensitive data in logs
  • Missing authentication checks
  • CORS misconfiguration
  • Open redirects

🟡 Medium

  • Missing rate limiting
  • Verbose error messages
  • Missing security headers
  • Insecure random number generation
  • Session fixation risks

🟢 Low

  • Debug mode enabled
  • Unnecessary dependencies
  • Outdated but non-vulnerable packages

3. Secret Detection

Scan for exposed secrets:

# Check for common secret patterns
grep -rn "password\s*=" --include="*.py" --include="*.js" --include="*.go" .
grep -rn "api_key\s*=" --include="*.py" --include="*.js" --include="*.go" .
grep -rn "secret\s*=" --include="*.py" --include="*.js" --include="*.go" .

Patterns to detect:

  • AWS access keys: AKIA[0-9A-Z]{16}
  • GitHub tokens: ghp_[a-zA-Z0-9]{36}
  • Generic API keys: [aA][pP][iI]_?[kK][eE][yY].*['\"][a-zA-Z0-9]{20,}['\"]
  • Private keys: -----BEGIN (RSA|EC|OPENSSH) PRIVATE KEY-----
  • JWT tokens: eyJ[a-zA-Z0-9_-]*\.eyJ[a-zA-Z0-9_-]*\.[a-zA-Z0-9_-]*

4. Configuration Security

Check:

  • .env files not in .gitignore
  • Debug/development settings in production configs
  • Default credentials
  • Overly permissive CORS
  • Missing HTTPS enforcement

Output Report

🛡️ Security Scan Report
══════════════════════════════════════════════════════════

🔴 CRITICAL (2)
───────────────
1. SQL Injection - src/db/queries.py:45
   Issue: User input directly in SQL query
   Fix: Use parameterized queries
   
2. Hardcoded Secret - src/config.py:12
   Issue: API key exposed in source code
   Fix: Move to environment variable

🟠 HIGH (3)
───────────────
1. Missing Auth Check - src/api/admin.py:23
   Issue: Admin endpoint lacks authentication
   Fix: Add @require_auth decorator

[... more items ...]

📦 Dependency Issues (5)
───────────────
- requests 2.25.0 → 2.31.0 (CVE-2023-32681)
- lodash 4.17.20 → 4.17.21 (Prototype pollution)

📊 Summary
───────────────
Critical: 2  |  High: 3  |  Medium: 5  |  Low: 8
Dependencies: 5 vulnerable

🔧 Auto-fixable: 6 issues
   Run /security-fix to apply safe fixes
══════════════════════════════════════════════════════════

Read the full file on GitHub · 150 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 150 lines · 11 tokens per session scan A cb7ddf453e22

Subscribe to this mod's changes

security-check is a command published in the GitHub repository dachivadachkoria/claude-code-starter-kit (4 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 1,021 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.