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/EZotoff/ez-omo-configWrote 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/commands/ezotoff/ez-omo-config/design-review)<a href="https://agentmods.dev/commands/ezotoff/ez-omo-config/design-review"><img src="https://agentmods.dev/badge/commands/ezotoff/ez-omo-config/design-review/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/commands/ezotoff/ez-omo-config/design-review"><img src="https://agentmods.dev/badge/commands/ezotoff/ez-omo-config/design-review.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.00012 | $0.00248 |
| Opus 5 | $0.00006 | $0.00124 |
| Sonnet 5 | $0.00002 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
design-review 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
Run a three-stage specialist design review on the design/proposal at hand. The composition is visible and editable — before spawning, restate the plan below and let the operator adjust stages, ordering, or models if they want; proceed as-adjusted.
Stage 1 — DRAFT: one artistry (or best available creative-generalist) agent produces the design/proposal draft from the brief. Give it full context and freedom on approach.
Stage 2 — CRITIQUE: one oracle agent reviews the draft for soundness: flaws, missing considerations, failure modes. It sees the draft but not stage 1's conversation.
Stage 3 — CHALLENGE: one agent in the mephistopheles category attacks the critiqued draft — adversarial pass on the strongest assumptions. It sees the draft and the critique.
Then synthesize: the final design incorporating what survived, with each material change attributed to which stage forced it, and the open disagreements stated plainly rather than smoothed over.
Boundary: this is analysis, not authorization — the output informs the operator's decision; nothing proceeds anywhere without them saying so.
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 · 16 lines · 12 tokens per session scan A fd31c560de8f
design-review is a command published in the GitHub repository EZotoff/ez-omo-config (6 stars, last pushed 6d ago), licensed MIT. It adds 12 tokens to every session and 248 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-06.
Other commands, from other repositories
/a11y-audit
Auditoría de accesibilidad WCAG 2.2 completa con escaneo de HTML/componentes. Detecta: alt text faltante, problemas de contraste, navegación por teclado, etiquetas ARIA, gestión de focus, jerarquía de encabezados, etiquetas de formularios. Genera reporte accionable con instrucciones de remediación.
/a11y-fix
Correcciones automáticas de accesibilidad con verificación y preview. Genera código de fix para issues detectados por /a11y-audit. Preview antes de aplicar. Verifica que no introduce nuevos problemas. Covers: alt text, ARIA attributes, focus traps, skip links, color contrast.
/a11y-report
Reporte de conformidad de accesibilidad para stakeholders y legal. Tres formatos: ejecutivo (resumen + score), técnico (detalles completos + código), legal (declaración VPAT/Section 508). Tracking de tendencias. Exportable.
design
Generate and update visual design assets per the project's design system.
theme
Switch between visual theme skins — OLED Black, Matrix, Claude Anthropic, Surprise Me.
a11y
You are a WCAG 2.1 Level AA accessibility specialist. You audit user interfaces for perceivable, operable, understandable, and robust compliance. You have zero tolerance for "we'll add a11y later" — accessibility is a launch requirement, not a polish step.