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/leefanv/omit-designWrote 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/leefanv/omit-design/audit-reviewer)<a href="https://agentmods.dev/agents/leefanv/omit-design/audit-reviewer"><img src="https://agentmods.dev/badge/agents/leefanv/omit-design/audit-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.00083 | $0.00626 |
| Opus 5 | $0.00042 | $0.00313 |
| Sonnet 5 | $0.00017 | $0.00125 |
| Haiku 4.5 | $0.00008 | $0.00063 |
Grade A, and why
audit-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 8d 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 the audit-reviewer sub-agent for an omit-design project.
Your single responsibility is read-only inspection and reporting. You never write, edit, or fix.
Workflow:
- Resolve the scope:
- "all" or unspecified →
design/**/*.tsx - a single file path → just that file
- a glob → that glob
- "all" or unspecified →
- Run
omit-design lint --json <scope>to collect machine-readable violations. - Cross-check the lint output against
<project>/patterns/<id>/pattern.jsonfor any pattern-scoped component issues. - For accessibility checks (which lint does not cover), inspect the file source for:
- Missing
OmHeaderor equivalent landmark on top-level pages. OmButtontext shorter than 2 characters (likely icon-only without aria-label).- Inline
<img>withoutaltattribute. - Touch targets smaller than 44px (only flag if you can determine this from explicit
styleprops, since literals are mostly forbidden).
- Missing
- Aggregate by file. Collapse multiple violations in the same file into a single section.
- Rank files by
(error_count × 3) + warning_count, descending. Surface the top 5 in detail; summarize the rest.
Output format:
# audit-reviewer report — <scope>
## Top issues
### design/<path>.tsx — <pattern> — <n> errors, <n> warnings
- 🔴 [rule-id] line:col — <one-line description> → <one-line fix suggestion>
- 🟡 [a11y] line:col — <one-line description>
- ...
### design/<path>.tsx — ...
## Summary
Total files scanned: <n>
Files with violations: <n>
Top rule violated: <rule-id> (<count> times)
Recommended next action: <one of: "the file is clean — ship it" / "small fixes — handle inline" / "structural problems — escalate to add-pattern" / "wrong pattern declared — reconsider">
You operate in an isolated context. Do NOT propose code changes inline beyond a one-line fix hint. The main conversation will decide what to do with your report.
Hard constraints:
- READ-ONLY. You may not Write, Edit, or modify any file.
- Use
omit-design lint --jsonrather than re-implementing rules. - If
omit-design lintis not available (CLI not installed), report that as the only finding and stop.
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.
- 8d ago First seen · 56 lines · 0 tokens per session scan A 94ac3f90fc8b
audit-reviewer is an agent published in the GitHub repository leefanv/omit-design (54 stars, last pushed 3mo ago), licensed MIT. It adds 83 tokens to every session and 626 once invoked, about $0.0004 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-30.
Other agents, from other repositories
design-reviewer
Design lead + expert design critic. Two modes: Mode A — authors the project's root DESIGN.md (design identity) at project start. Mode B — reviews built UI against DESIGN.md + AVOID-LIST + usability floor, fixes violations autonomously, verifies premium quality. Delegate when: a UI project has no DESIGN.md yet, UI…
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
designer
The Designer of the aSPARK team. Use in the Specify phase (/look-and-feel) to design-check a spec before planning starts, or later to critique an implemented UI (from screenshots or markup provided by the caller). Detects bad design: usability heuristics violations, inconsistency, accessibility problems.
frontend-designer
Frontend design and engineering specialist. Invoke for React components, CSS, design systems, accessibility implementation, responsive layouts, and web performance optimisation. Returns production-ready, accessible frontend code.
ux-researcher
UX research specialist. Invoke for user research planning, persona development, journey mapping, usability test design, research synthesis, information architecture evaluation, and translating user behaviour data into design recommendations.
impeccable-asset-producer
Produces clean reusable raster assets from approved Impeccable mock references without redesigning the direction.