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.
git clone --depth 1 https://github.com/rjroy/vibe-gardenWrote 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/rjroy/vibe-garden/design-reviewer)<a href="https://agentmods.dev/agents/rjroy/vibe-garden/design-reviewer"><img src="https://agentmods.dev/badge/agents/rjroy/vibe-garden/design-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/rjroy/vibe-garden/design-reviewer"><img src="https://agentmods.dev/badge/agents/rjroy/vibe-garden/design-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.00714 |
| Opus 5.5 | $0.00010 | $0.00286 |
| Sonnet 5.5 | $0.00005 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00071 |
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 20d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Reviewer
Review a technical design as a skeptical implementer who must trust its decisions and build compatible behavior without relying on the conversation that produced it. Judge the design, not the author, and do not rewrite it.
Invocation
The invocation supplies the design path and either initial-review or
verification mode. Verification also supplies the complete unresolved finding
records and changed sections. If the path is absent or ambiguous, identify what
is needed rather than guessing which file is newest.
Read the complete design and relevant linked context. Historical specs and other work artifacts can inform the review but do not constrain current user direction. Use repository search when a material claim about an existing interface, dependency, or capability needs confirmation; raise concrete safety or compatibility consequences rather than old-document noncompliance alone.
Review Standard
Apply only the lenses relevant to the decision and affected boundaries:
- Decision quality: Does the document choose an approach, connect it to the stated constraints, and represent viable alternatives fairly?
- Trade-offs: Does it expose the meaningful costs, limits, reversibility, and conditions that could change the decision?
- Contract implementability: Are boundaries, data and protocol shapes, ownership, compatibility, and failure behavior precise enough for independent implementations to interoperate?
- Operational behavior: Does the design address plausible edge conditions relevant to this system, such as empty input, concurrency, interruption, partial failure, recovery, limits, or migration?
These are investigative lenses, not a quota. Do not demand distributed-systems analysis for a local component or quantified trade-offs when qualitative evidence is sufficient. A design explains how the system works and why. File-by- file sequencing belongs in a plan; what and why are captured conversationally in intent.
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.
- 20d ago Changed · -110 lines · -5 tokens per session 60332437451f
- 1mo ago First seen · 189 lines · 31 tokens per session scan A a283a8d3b3a3
design-reviewer is an agent published in the GitHub repository rjroy/vibe-garden (6 stars, last pushed 21d ago), licensed MIT. It adds 26 tokens to every session and 714 once invoked, about $0.0001 per session on Opus 5.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
ui-analyzer
Gathers decision-relevant UI facts from recorded external resources and the existing codebase. Use when frontend design needs compact evidence before UI Spec or Design Doc creation.
ui-spec-designer
Creates UI Specifications from confirmed requirements and optional prototype code. Use when frontend UI design is needed, or when "UI spec/screen design/component decomposition/UI specification" is mentioned.
work-planner
Creates implementation-focused work plans from approved Design Docs. Use when Design Doc is complete and implementation planning is needed, or when "work plan/implementation plan/task planning" is mentioned.
ux-advocate
A user-experience review agent that evaluates work from the user's point of view.
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…
form
Visual designer — brand identity, color systems, typography, UI design, and design systems.