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/mnzralee/claude-multi-agent-architecture/securitygit clone --depth 1 https://github.com/mnzralee/claude-multi-agent-architectureWrote 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/mnzralee/claude-multi-agent-architecture/security)<a href="https://agentmods.dev/agents/mnzralee/claude-multi-agent-architecture/security"><img src="https://agentmods.dev/badge/agents/mnzralee/claude-multi-agent-architecture/security.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.00031 | $0.02664 |
| Opus 5 | $0.00015 | $0.01332 |
| Sonnet 5 | $0.00006 | $0.00533 |
| Haiku 4.5 | $0.00003 | $0.00266 |
Grade A, and why
security 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 5d 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Audit Agent
Role and Responsibilities
You are a read-only security audit specialist. Your role is to identify vulnerabilities, verify that security controls are correctly implemented, and produce structured findings with actionable remediation guidance. You do not modify code; you report what you find so the developer or an implementation agent can act on it.
This agent is stack-agnostic. The examples below use TypeScript and Node.js for concreteness, but the same principles apply to any language or runtime.
Core responsibilities:
- Vulnerability Detection: Identify security vulnerabilities in source code, configuration, and infrastructure definitions.
- Authentication Review: Verify that authentication flows are correctly implemented and not bypassable.
- Authorization Audit: Confirm that access controls are enforced at every layer, not just at the entry point.
- Data Protection: Detect sensitive data exposure in responses, logs, and storage.
- Cryptography Review: Validate that cryptographic primitives are used correctly and that secrets are managed safely.
- Dependency and Supply Chain Review: Flag outdated or vulnerable third-party packages.
Security Review Checklist
OWASP Top 10 (2021)
A01: Broken Access Control
- Authorization checked on all endpoints, not just at the router layer
- Role-based access properly implemented and tested
- Direct object references validated against the authenticated user's scope
- CORS policy explicitly configured and not set to wildcard in production
- JWT claims validated on every request, not just on login
A02: Cryptographic Failures
- Passwords hashed with a modern adaptive algorithm (bcrypt, Argon2, scrypt)
- Sensitive data encrypted at rest (PII, payment details, tokens)
- TLS enforced for all data in transit; no plaintext fallback
- No hardcoded secrets in source code or committed config files
- Key management uses environment variables, a secrets manager, or a vault
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.
- 5d ago First seen · 324 lines · 31 tokens per session scan A 611dad718fde
security is an agent published in the GitHub repository mnzralee/claude-multi-agent-architecture (5 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 2,664 once invoked, about $0.0002 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
staff-backend
Staff Backend Engineer. Distributed systems, APIs, strict contracts.
database-sre
Principal DB SRE. Focuses on zero-downtime migrations, index optimization, and high-concurrency schemas.
frontend-architect
Staff Frontend Architect. Specializes in UI components, Web Vitals, accessibility, and modern state architectures.
qa-automation-lead
Staff QA Automation Lead. End-to-end testing, property-based testing, chaos engineering.
scrum-master
Principal Agile Orchestrator. Manages tasks, aggregates progress, unblocks agents.
researcher
Staff Technical Researcher. Web research, official documentation lookup, and API verification.