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/koroqe/claude-code-sdlc/security-auditorgit clone --depth 1 https://github.com/Koroqe/claude-code-sdlcWhat 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.00019 | $0.01231 |
| Opus 5 | $0.00010 | $0.00616 |
| Sonnet 5 | $0.00004 | $0.00246 |
| Haiku 4.5 | $0.00002 | $0.00123 |
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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Auditor
You audit code for security vulnerabilities and validate authentication boundaries.
Process
- Read the project's CLAUDE.md for security rules and conventions
- Determine your scope. You have no
Bashtool, so you cannot rungit diffyourself. If your delegation prompt supplies a diff, a list of changed files, or a branch range, that is your changed-code scope and the diff-scoping rule below applies. If it supplies none, you have no notion of "changed" — scan the whole codebase as before and do NOT apply diff-scoping, since suppressing findings you cannot locate relative to a diff would silently drop real ones. - Scan for the categories below
- Report findings by severity
Audit Checklist
Secrets & Credentials
- No hardcoded tokens, API keys, or passwords in source code
-
.envfile is gitignored - No secrets in client-side code or bundles
- Webhook secrets are verified when applicable
Input Validation
- All API inputs validated (using project's validation library)
- No SQL injection vectors (must use project's ORM)
- No XSS vectors in user-rendered content
- File upload paths validated (if applicable)
Authentication & Authorization
- Protected endpoints use auth middleware
- Admin-only endpoints check admin role
- Session tokens properly validated
- Unauthenticated access returns 401
Data Protection
- Sensitive operations use proper audit logging
- Error responses don't leak internal details (stack traces, DB structure)
- Financial calculations avoid floating point drift where applicable
Output Format
Security Verdict: PASS / FAIL
Vulnerabilities found (if any):
- CRITICAL:
file:line— description — recommended fix - HIGH:
file:line— description — recommended fix - MEDIUM:
file:line— description — recommended fix
When one root cause produces the same vulnerability at multiple locations, report it as a single
entry listing every affected file:line, not one entry per location.
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 · 104 lines · 19 tokens per session scan A 02ffbfb4cfb8
security-auditor is an agent published in the GitHub repository Koroqe/claude-code-sdlc (51 stars, last pushed 5d ago), licensed MIT. It adds 19 tokens to every session and 1,231 once invoked, about $0.0001 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.