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 commands/adilkalam/orca/design-auditgit clone --depth 1 https://github.com/adilkalam/orcaWrote 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/adilkalam/orca/design-audit)<a href="https://agentmods.dev/commands/adilkalam/orca/design-audit"><img src="https://agentmods.dev/badge/commands/adilkalam/orca/design-audit.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.00089 | $0.01449 |
| Opus 5 | $0.00044 | $0.00724 |
| Sonnet 5 | $0.00018 | $0.00290 |
| Haiku 4.5 | $0.00009 | $0.00145 |
Grade A, and why
design-audit 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design-audit
Entry: mandatory skill loading
Target routing (#PATH_DECISION — one rule, not 5 copies): apply ~/.claude/docs/concepts/ios-design-contract/target-routing.md. If the TARGET ends in .swift, load Skill("ios-impeccable-hub") in place of impeccable-hub and use the Swift detector + iOS banned-rule bullets below; otherwise keep the CSS/web path unchanged.
Before any work, invoke:
Skill("impeccable-hub")— the aesthetic (felt-state spine + banned rules + preferences + voice-anchors + detector floor). Baseline for every invocation. For a.swifttarget, loadSkill("ios-impeccable-hub")instead (SwiftUI banned rules + preferences + the iOS detector contract) — see the routing rule above.Skill("ui-quality-audit")— the ui-quality-audit skill's technical quality checks (a11y, performance, responsive, anti-patterns).
Context gathering
Read the current project's .claude/PRODUCT.md (strategic register) and .claude/DESIGN.md (visual contract). If absent, do NOT block — run the audit on the hub's global aesthetic (the banned rules + preferences + voice-anchors still drive the anti-pattern flags) and note once: "No project contract found — auditing against the global aesthetic; run /impeccable --teach to make this project-specific."
Read the global catalog references that matter for audit:
~/.claude/docs/concepts/design-contract/banned/— the anti-pattern files drive which anti-patterns to flag.~/.claude/docs/concepts/design-contract/preferences/alignment-precision.md— 7 optical rules + pixel audit are part of the technical-quality pass.
Work
Apply the ui-quality-audit skill's procedures to the user's target. Extend with Adil's aesthetic:
- Flag every Tailwind palette utility or Tailwind hex value (P0 —
banned/colors.md). - Flag every reflex-font usage (P0 —
banned/fonts.md). - Flag every AI-purple / AI-magenta / AI-pink gradient (P0 —
banned/gradients.md). - Flag every chamfer stack (inset-highlight + outer shadow + gradient on same element; P0 —
banned/chamfered-buttons.md). - Flag every default-ease transition and bouncy easing (P1 —
banned/motion-suddenness.md). - Flag every side-stripe border (
border-left/border-right> 1px; P0 —banned/chamfered-buttons.md/ Bakaus absolute_bans). - Flag every gradient text (
background-clip: text+ gradient; P0 — Bakaus absolute_bans).
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 · 71 lines · 89 tokens per session scan A 3d056b2d7a10
design-audit is a command published in the GitHub repository adilkalam/orca (2 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 1,449 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-31.
Other commands, from other repositories
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
template-ui
Design a Sent template-builder interface.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
study
Runtime entry point for extracting design DNA from a live URL, screenshot, or reference site. Part of the Discovery lifecycle phase.
4-generate
Run Stage 4 of the design system skill generation pipeline: parallel skill file generation.
audit-ux
Whole-repo adversarial UX audit of the shipped user surfaces -> docs/audits/ux-audit- .md.