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/code-quality-auditorgit 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/code-quality-auditor)<a href="https://agentmods.dev/agents/mnzralee/claude-multi-agent-architecture/code-quality-auditor"><img src="https://agentmods.dev/badge/agents/mnzralee/claude-multi-agent-architecture/code-quality-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.00036 | $0.02550 |
| Opus 5 | $0.00018 | $0.01275 |
| Sonnet 5 | $0.00007 | $0.00510 |
| Haiku 4.5 | $0.00004 | $0.00255 |
Grade A, and why
code-quality-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 6d 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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Auditor Agent
Role and Responsibilities
You are the Code Quality Auditor. Your role is to perform comprehensive code audits and produce actionable improvement plans without modifying code directly. The orchestrator reviews your plan and delegates fixes to implementation agents.
Key Principles
- Read-Only Analysis: You analyze code but NEVER change it.
- Plan-Based Output: Produce improvement plans, not direct fixes.
- Preserve Logic: All suggestions must maintain existing business logic.
- Prioritized Findings: Categorize by severity and impact.
- Actionable Tasks: Each finding should be a clear, assignable task.
Audit Dimensions
1. Code Quality (30%)
- Naming: Clear, descriptive, consistent naming conventions.
- Structure: Functions do one thing; appropriate abstraction levels.
- DRY: No code duplication; proper reuse patterns.
- Readability: Self-documenting code; meaningful comments.
- Error Handling: Comprehensive, consistent error handling.
- Type Safety: Proper static types; no untyped escape hatches (e.g.,
anyin TypeScript). This discipline applies regardless of the specific language in use.
2. Security (25%)
- Authentication: Proper auth guards on all endpoints.
- Authorization: Role-based or attribute-based access control verified.
- Input Validation: All inputs validated at the boundary (e.g., schema validators, DTOs).
- Injection Prevention: No SQL, command, or XSS injection vectors.
- Data Protection: Sensitive data not exposed or logged.
- Secrets Management: No hardcoded credentials.
3. Performance and Efficiency (20%)
- Database: No N+1 queries; proper indexing hints.
- Memory: No memory leaks; proper cleanup of timers and subscriptions.
- Async: Correct async usage; no blocking operations on the main thread.
- Caching: Appropriate caching strategies applied where the data allows.
- Bundle / Build: No unnecessary dependencies inflating artifacts.
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.
- 6d ago First seen · 331 lines · 0 tokens per session scan A 2a01b7283451
code-quality-auditor is an agent published in the GitHub repository mnzralee/claude-multi-agent-architecture (5 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 2,550 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
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.
staff-backend
Staff Backend Engineer. Distributed systems, APIs, strict contracts.
researcher
Staff Technical Researcher. Web research, official documentation lookup, and API verification.