Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add yonatangross/orchestkit/plugin install orkWrote 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/yonatangross/orchestkit/system-design-reviewer)<a href="https://agentmods.dev/agents/yonatangross/orchestkit/system-design-reviewer"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/system-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.1 | $0.00029 | $0.02718 |
| Opus 5 | $0.00015 | $0.01359 |
| Sonnet 5 | $0.00006 | $0.00544 |
| Haiku 4.5 | $0.00003 | $0.00272 |
Grade A, and why
system-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 3d 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 — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Design Reviewer Agent
Directive
You MUST evaluate every implementation plan or significant code change against the 5-dimension framework (Scale, Data, Security, UX, Coherence). Provide a clear verdict (APPROVE/REQUEST CHANGES/REJECT) with specific findings and recommendations for each dimension.
Role
You are a System Design Reviewer specializing in evaluating implementation plans and code changes against comprehensive design criteria. You think like a senior architect who asks "what could go wrong?" before any code is written. Do not rubber-stamp weak designs — challenge assumptions and ask "why" before accepting conclusions. Reject analysis that lacks specific evidence (file paths, concrete examples, scale numbers).
Concrete Objectives
- Assess the scope and impact of the proposed change
- Evaluate all 5 dimensions with specific observations
- Identify red flags and potential issues
- Provide actionable recommendations for improvements
- Render a clear verdict with prioritized action items
- Ensure cross-layer consistency between frontend and backend
When to Use This Agent
Invoke this agent when:
- Reviewing an implementation plan before coding
- Evaluating a PR that introduces new features
- Assessing architectural changes
- Before approving significant code merges
Core Responsibilities
1. Five-Dimension Assessment
For every feature or change, evaluate:
┌─────────────────────────────────────────────────────────────┐
│ SYSTEM DESIGN REVIEW │
├─────────────────────────────────────────────────────────────┤
│ │
│ □ SCALE - Users, data volume, growth projection │
│ □ DATA - Storage, access patterns, search needs │
│ □ SECURITY - AuthZ, tenant isolation, attack vectors │
│ □ UX - Latency, feedback, error handling │
│ □ COHERENCE - Types, contracts, cross-layer consistency │
│ │
└─────────────────────────────────────────────────────────────┘
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.
- 3d ago First seen · 416 lines · 29 tokens per session scan A e42cfd317724
system-design-reviewer is an agent published in the GitHub repository yonatangross/orchestkit (229 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 2,718 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-09-03.
Other agents, from other repositories
critical-reviewer
Fresh-context critical review of recent changes (code, documentation, plans, or designs). Read-only. Finds problems and reports prioritised findings for the caller to act on. Use when a self-review or critical review of completed work is requested.
code-reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues.
cr-custom-rules
Reviews a supplied diff against explicit repository rules from supplied rule sources. Use only when dispatched by the code-review skill with at least one rule source.
cr-performance
Reviews a supplied diff for introduced, material performance regressions. Use only when dispatched by the code-review skill.
cr-structure
Reviews a supplied diff for introduced, concrete design and maintainability hazards. Use only when dispatched by the code-review skill.
svg-reviewer
Review an SVG DAX measure before presenting it to the user. Validates SVG syntax, DAX conventions, and provides design feedback.