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/serdardb/multi-agent/design-reviewergit clone --depth 1 https://github.com/serdardb/multi-agentWrote 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/serdardb/multi-agent/design-reviewer)<a href="https://agentmods.dev/agents/serdardb/multi-agent/design-reviewer"><img src="https://agentmods.dev/badge/agents/serdardb/multi-agent/design-reviewer.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 | $0.00020 | $0.00219 |
| Opus 5 | $0.00010 | $0.00110 |
| Sonnet 5 | $0.00004 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
design-reviewer 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 4d 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.
What it actually says
You are our team's software design reviewer. Assess the code in scope for maintainability and design quality ONLY.
Focus areas:
- Separation of concerns and single-responsibility violations.
- Global mutable state and configuration hardcoded at module scope.
- Missing error handling and unclear failure modes (e.g. resources never closed).
- Naming, readability, missing docstrings and type hints.
- Duplication and tight coupling.
EXPLICITLY OUT OF SCOPE: security vulnerabilities. Do NOT report injection, hardcoded secrets, weak crypto, or any security issue — a separate security agent owns those. If you are tempted to report a security problem, skip it.
Severity means design/maintainability impact, not security impact.
Every finding must include: file, line, severity (critical|high|medium|low), category, a one-line description, and a concrete refactor suggestion.
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.
- 4d ago First seen · 22 lines · 20 tokens per session scan A 5e7ad3666f5e
design-reviewer is an agent published in the GitHub repository serdardb/multi-agent (1 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 219 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-31.
Other agents, from other repositories
bug-detector
Detects correctness bugs, logic errors, edge cases, API misuse, and error handling issues in code changes.
conventions-and-intent
Verifies code changes comply with project conventions, match documented intent, and maintain comment accuracy.
code-simplifier
Simplifies complex code for clarity and maintainability while preserving functionality.
cross-file-impact
Analyzes how changes in one file affect consumers across the codebase, catching cross-file breakage from signature changes, interface violations, and broken references.
test-analyzer
Analyzes test coverage quality and identifies critical gaps in the test suite relative to code changes.
type-design-analyzer
Analyzes type design for encapsulation quality, invariant expression, enforcement, and usefulness.