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/imsaif/design-with-claudeWrote 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/imsaif/design-with-claude/design-triage)<a href="https://agentmods.dev/commands/imsaif/design-with-claude/design-triage"><img src="https://agentmods.dev/badge/commands/imsaif/design-with-claude/design-triage/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/imsaif/design-with-claude/design-triage"><img src="https://agentmods.dev/badge/commands/imsaif/design-with-claude/design-triage.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.00033 | $0.01657 |
| Opus 5 | $0.00016 | $0.00829 |
| Sonnet 5 | $0.00007 | $0.00331 |
| Haiku 4.5 | $0.00003 | $0.00166 |
Grade A, and why
design-triage 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 10d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You take an audit report full of findings and turn it into an ordered plan someone can actually work through — then you work through it. When invoked with $ARGUMENTS, you read the most recent .dwic/audit-*.md, rank what it found by what genuinely ships worst, and fix in that order.
npx dwic-audit tells the user what is wrong and stops. Nothing carries them from finding to fix, so a 40-finding report gets read once and abandoned. You are that missing step.
The evidence rule
You are reading source, not looking at a rendered screen. Source determines which token or value was used, what the markup and semantics are, whether a library default was left untouched, and what the copy says. It does not determine visual balance, focal point, relative prominence, whether something "looks" right, or anything measured at runtime (frame rate, load time, layout shift, zoom reflow).
- Judge from source only what source determines.
- If you can render it — dev server, screenshot, browser tooling — do that first, and say you did.
- If you cannot render, say so plainly and mark every appearance or runtime claim
unverified — needs rendering. - Human or assistive-technology testing (screen readers, real users, colour-blindness simulation) is a recommendation to the user, never something you report as done.
Never state as fact something you inferred from a class name. A finding you cannot support is worse than a finding you did not make.
Skip this command when
- There is no
.dwic/audit-*.mdand the user does not want one generated. Runnpx dwic-auditfirst, or use/design-briefif they want guidance rather than a fix pass. - The audit came back clean. Say so and stop; do not hunt for work.
- The user has one specific known problem. Go straight to that specialist — triage is for a pile of findings, not a single one.
Step 0: get a report
ls -t .dwic/audit-*.md | head -1
- Found one — read it, and note its date. If it is more than a few days old, say so and offer to re-run
npx dwic-audit, since findings may be stale. - None found — offer to run
npx dwic-auditnow. It needs no token and nothing leaves the machine. - User passed a path or pasted a report in $ARGUMENTS — use that instead.
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.
- 10d ago First seen · 136 lines · 33 tokens per session scan A 365185c5eb2f
design-triage is a command published in the GitHub repository imsaif/design-with-claude (11 stars, last pushed 20d ago), licensed MIT. It adds 33 tokens to every session and 1,657 once invoked, about $0.0002 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 commands, from other repositories
audit
Run a full UI/UX design audit on the current project. Scores 12 dimensions and produces a markdown report with prioritized findings.
a11y
Run an accessibility-only audit — focus indicators, skip links, alt text, prefers-reduced-motion, WCAG contrast. Scoped variant of /ui-ux-suite:audit.
colors
Run a color-only design audit — contrast, near-duplicates, dark mode, semantic coverage. Scoped variant of /ui-ux-suite:audit.
components
Run a component-quality audit — state coverage, primitive consistency, cn()/CVA patterns. Scoped variant of /ui-ux-suite:audit.
typography
Run a typography-only audit — scale detection, font count, body size, line height, fluid type. Scoped variant of /ui-ux-suite:audit.
make-creative
Design and produce any fixed-canvas creative — poster, flyer, brochure, business card, social post/ad, story, thumbnail, event banner/signage, infographic, or email — correctly spec'd and on-brand.