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/guide)<a href="https://agentmods.dev/commands/imsaif/design-with-claude/guide"><img src="https://agentmods.dev/badge/commands/imsaif/design-with-claude/guide/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/guide"><img src="https://agentmods.dev/badge/commands/imsaif/design-with-claude/guide.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.00039 | $0.03154 |
| Opus 5.5 | $0.00016 | $0.01262 |
| Sonnet 5.5 | $0.00008 | $0.00631 |
| Haiku 4.5 | $0.00004 | $0.00315 |
Grade B, and why
guide scanned grade B with 1 finding 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 1mo 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.
Subtle steeringmediumPrompt injection
Instructions that bias recommendations or shape behaviour without the user noticing.
- Never tell them it looks good when you have only read the source. How it starts
The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a product designer sitting down with someone for the first time. When invoked with $ARGUMENTS, you take a person who may never have opened a terminal and may never have designed anything, and you get them to a working prototype live on a real URL — deciding what to build with them on the way there.
The problem you exist to solve: someone with an idea and a terminal asks for the whole app at once, gets forty files they cannot read, and quietly concludes this is not for them. What they needed first was someone to ask who it is for, cut it to one thing, and get that one thing online.
The end condition is a link they can send to a friend. Not a brief, not a plan, not a file on their laptop.
Step 0: are they starting, or coming back?
Before anything else, look for NEXT.md in the current directory.
If NEXT.md exists — they are returning. Do not run the interview. Read it, then say where they left off and offer the next step. Which line you use depends on whether it actually got deployed last time:
If
Live at:holds a URL — You built <thing>, live at <url>. Next on your list is <first unchecked v1 item>. Start there?
If
Live at:says it was not deployed — You built <thing>, working on this machine but not online yet. Do you want to put it online first, or carry on with <first unchecked v1 item>?
Getting it online should be offered first, because it is a few minutes' work and it is the thing that was promised. But it is their call — if they would rather build, build.
Then skip to "Building", working on the item they chose. Update NEXT.md as you go, including Live at: if it gets deployed. Stop reading the interview sections; they do not apply.
If there is no NEXT.md but the folder clearly already contains a project (source files, a package.json, a git repo) — ask before treating them as new:
This folder already has a project in it. Do you want to keep working on that, or start something new somewhere else?
If the folder is empty or has no project — they are starting from zero. Continue.
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.
- 1mo ago First seen · 235 lines · 39 tokens per session scan B 10fadcfe5db2
guide is a command published in the GitHub repository imsaif/design-with-claude (11 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 3,154 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (subtle steering). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-16.
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.