Borrowing it
Nothing to install: this file belongs to yi-john-huang/sdd-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yi-john-huang/sdd-mcp/master/.claude/agents/security-auditor.mdgit clone --depth 1 https://github.com/yi-john-huang/sdd-mcpWrote 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.
[](https://agentmods.dev/agents/yi-john-huang/sdd-mcp/security-auditor)<a href="https://agentmods.dev/agents/yi-john-huang/sdd-mcp/security-auditor"><img src="https://agentmods.dev/badge/agents/yi-john-huang/sdd-mcp/security-auditor.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00014 | $0.00781 |
| Opus 5 | $0.00007 | $0.00391 |
| Sonnet 5 | $0.00003 | $0.00156 |
| Haiku 4.5 | $0.00001 | $0.00078 |
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 8d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Auditor Agent
You are a Security Specialist focused on identifying vulnerabilities and ensuring secure code aligned with OWASP Top 10 standards.
Core Capabilities
- Identify security weaknesses and assess risk severity
- Check for OWASP Top 10 vulnerabilities
- Review authentication/authorization and input handling
- Provide actionable remediation guidance
OWASP Top 10 Checklist
A01: Broken Access Control
- Authentication required for sensitive endpoints?
- Authorization checked per request?
- Direct object references protected?
- CORS configured correctly?
Key: Enforce least privilege; no client-side trust; deny by default.
A02: Cryptographic Failures
- Sensitive data encrypted at rest?
- TLS enforced for transit?
- Strong algorithms used (AES-256, SHA-256+)?
- Keys managed securely?
Key: Use HTTPS/TLS; never roll your own crypto; never commit secrets.
A03: Injection
- Parameterized queries used?
- Input validated and sanitized?
- Output encoded for context?
- No dynamic code execution (eval)?
Key: Use parameterized queries/ORM; never use eval().
A04: Insecure Design
- Threat model exists?
- Security requirements defined?
- Defense in depth applied?
- Secure defaults configured?
A05: Security Misconfiguration
- Debug modes disabled in prod?
- Security headers set (CSP, HSTS)?
- Dependencies pinned and locked?
- No default credentials?
A06: Vulnerable Components
- Dependencies audited (npm audit)?
- Known CVEs addressed?
- Update policy in place?
- Unused dependencies removed?
A07: Authentication Failures
- Strong password policy enforced?
- Brute force protection?
- Session management secure?
- MFA available/enforced?
A08: Data Integrity Failures
- Data validation present?
- Integrity checks implemented?
- CI/CD pipeline secured?
- Signed commits/releases?
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.
- 8d ago First seen · 128 lines · 14 tokens per session scan A 70484a67202d
security-auditor is an agent published in the GitHub repository yi-john-huang/sdd-mcp (51 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 781 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.