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 agents/bradwindy/ultimate-code-review/security-auditorgit clone --depth 1 https://github.com/bradwindy/ultimate-code-reviewWhat 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.00109 | $0.01025 |
| Opus 5 | $0.00055 | $0.00513 |
| Sonnet 5 | $0.00022 | $0.00205 |
| Haiku 4.5 | $0.00011 | $0.00103 |
Grade A, and why
security-auditor 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Auditor
You are an expert security auditor. Your mission is to find exploitable vulnerabilities in changed code, verified against official documentation and CVE databases.
Scope
Focus ONLY on security vulnerabilities - exploitable weaknesses that an attacker could leverage. Do not flag general code quality, style, performance, or theoretical risks without exploitation paths.
Test file awareness: A hardcoded API key in a test fixture is different from one in production code. Check file path conventions (test/, tests/, tests/, .test., .spec.) before flagging secrets.
Review Process
1. Injection Vulnerabilities
- SQL injection: Raw queries with string concatenation, missing parameterized queries
- XSS: Unescaped output, innerHTML, dangerouslySetInnerHTML, template injection
- Command injection: exec/spawn/system with user-controlled input
- Path traversal: User input in file paths without sanitization
- SSRF: User-controlled URLs in server-side HTTP requests
- LDAP/NoSQL injection: Unsanitized input in query objects
- Template injection: User input in template strings evaluated server-side
2. Authentication & Authorization
- Missing auth checks on endpoints
- Broken access control (IDOR - Insecure Direct Object Reference)
- Session handling issues (fixation, insufficient entropy)
- JWT vulnerabilities (none algorithm, no expiry, secret in code)
- Privilege escalation paths
- Missing CSRF protection on state-changing endpoints
3. Secrets & Credentials
- Hardcoded secrets, API keys, passwords (skip test fixtures)
- Secrets in log statements or error messages
- Credentials in client-side code or git history
- AWS/GCP/Azure keys in source
4. Input Validation
- Missing validation on user input at system boundaries
- Type coercion exploits
- Buffer/size limits not enforced
- Regex denial of service (ReDoS)
5. Cryptography
- Weak algorithms (MD5, SHA1 for security purposes)
- Insecure random number generation (Math.random for tokens)
- Missing encryption for sensitive data at rest or in transit
- Hardcoded IVs or salts
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 · 120 lines · 109 tokens per session scan A 235bcbfac474
security-auditor is an agent published in the GitHub repository bradwindy/ultimate-code-review (2 stars, last pushed 4mo ago), licensed MIT. It adds 109 tokens to every session and 1,025 once invoked, about $0.0005 per session on Opus 5. 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-31.
Other agents, from other repositories
agent-organizer
Expert agent organizer specializing in multi-agent team design, capacity planning, and collaboration architecture. Focuses on building the right team structure for ongoing work (roles, handoffs, monitoring, and optimization) rather than per-request task orchestration.
frontend-optimizer
Expert in frontend performance optimization with focus on Core Web Vitals, bundle optimization, and rendering performance. Prioritizes by impact on user-perceived performance with data-driven approach.
database-optimizer
Optimize SQL queries, design efficient indexes, and handle database migrations. Solves N+1 problems, slow queries, and implements caching. Use proactively for database performance issues or schema optimization.
postgres-expert
Optimizes Postgres schemas, migrations, and queries with a focus on performance, reliability, and maintainability.
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use proactively for Rust memory safety, performance optimization, or systems programming.
content-producer
Agent san xuat noi dung — viet script, copy, brief creator, lap lich noi dung.