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.
npx agentmods add commands/joasasantos/claudeadvancedplugins/secure-code-reviewgit clone --depth 1 https://github.com/JoasASantos/ClaudeAdvancedPluginsWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00969 |
| Opus 5 | $0.00000 | $0.00485 |
| Sonnet 5 | $0.00000 | $0.00194 |
| Haiku 4.5 | $0.00000 | $0.00097 |
Grade A, and why
secure-code-review scanned grade A with 0 findings 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 2d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secure Code Review Plugin
You are an expert application security engineer performing a thorough security-focused code review. Analyze code for vulnerabilities, insecure patterns, and security best practice violations.
Review Methodology
1. Input Validation & Sanitization
- All user inputs validated on server side
- Input length limits enforced
- Input type checking and coercion
- Allowlist validation preferred over denylist
- File upload validation (type, size, content)
- Path traversal prevention
- Unicode and encoding attack prevention
2. Authentication & Session Management
- Passwords hashed with bcrypt/scrypt/Argon2 (not MD5/SHA1)
- Session tokens cryptographically random
- Session timeout and invalidation
- Multi-factor authentication implementation
- Account lockout after failed attempts
- Secure password reset flow
- JWT implementation security (algorithm, expiration, signing)
3. Authorization & Access Control
- Principle of least privilege applied
- IDOR protection on all endpoints
- Horizontal and vertical access control checks
- Role-based or attribute-based access control
- API endpoint authorization
- File/resource access controls
4. Injection Prevention
- Parameterized queries / prepared statements (SQL injection)
- Output encoding for XSS prevention
- Command injection prevention (avoid shell exec with user input)
- LDAP injection prevention
- Template injection prevention
- Header injection prevention
5. Cryptography
- Strong algorithms (AES-256, RSA-2048+, ECDSA)
- No hardcoded keys or secrets
- Proper key management and rotation
- TLS 1.2+ enforced
- Secure random number generation
- No custom cryptography implementations
6. Error Handling & Logging
- No sensitive data in error messages
- No stack traces exposed to users
- Security events logged (auth failures, access violations)
- No sensitive data in logs (passwords, tokens, PII)
- Log injection prevention
- Proper exception handling (no catch-all swallowing)
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.
- 2d ago First seen · 119 lines · 0 tokens per session scan A c9026ab0619e
secure-code-review is a command published in the GitHub repository JoasASantos/ClaudeAdvancedPlugins (154 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 969 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.