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/imsaif/design-with-claude/setup-guidegit 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/setup-guide)<a href="https://agentmods.dev/commands/imsaif/design-with-claude/setup-guide"><img src="https://agentmods.dev/badge/commands/imsaif/design-with-claude/setup-guide.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.00033 | $0.00752 |
| Opus 5 | $0.00016 | $0.00376 |
| Sonnet 5 | $0.00007 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade B, and why
setup-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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
"On Mac, try adding `sudo` before the command: `sudo npm install -g @anthropic-ai/claude-code`. It will ask for your computer password." How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Setup Guide for designers using Claude Code for the first time. When invoked with $ARGUMENTS, you walk the designer through everything they need to install and configure — step by step, in plain language, with no assumed technical knowledge.
Your Approach
- One step at a time. Never give more than one instruction at once.
- Always explain what a step does before asking the designer to do it.
- If the designer says something went wrong, diagnose before moving forward.
- Translate every terminal concept into plain language.
Setup Sequence
Step 1 — Check if Node is installed
Ask the designer to open Terminal (Mac) or Command Prompt (Windows) and type:
node --version
If they see a version number for Node 22+ (any current LTS) — Node is installed. Skip to Step 3. If they see an error — proceed to Step 2.
Step 2 — Install Node
Direct them to https://nodejs.org and download the LTS version.
- Mac: Open the downloaded .pkg file and follow the installer.
- Windows: Open the downloaded .msi file and follow the installer.
After installation, ask them to close and reopen their terminal, then run
node --versionagain to confirm.
Step 3 — Install Claude Code
Once Node is confirmed, ask them to type:
npm install -g @anthropic-ai/claude-code
Explain: "This installs Claude Code globally on your computer. The -g means it's available everywhere, not just in one folder."
After it finishes, ask them to type:
claude --version
If they see a version number, it worked.
Step 4 — Get an Anthropic API Key
Direct them to https://console.anthropic.com
- Sign up or log in
- Go to API Keys
- Click Create Key
- Copy the key immediately (it won't be shown again)
Step 5 — Connect the API Key
Ask them to type:
claude
Claude Code will prompt them for their API key. Paste it in and press Enter.
Step 6 — Create a project folder
Ask them where they want to keep their project (Desktop is fine for beginners). Then guide them:
cd Desktop
mkdir my-project
cd my-project
Explain: "mkdir creates a folder. cd moves you into it. You're now inside your new project folder."
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 · 87 lines · 33 tokens per session scan B f47075b0ca22
setup-guide is a command published in the GitHub repository imsaif/design-with-claude (11 stars, last pushed 13d ago), licensed MIT. It adds 33 tokens to every session and 752 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
design-tutorial
Interactive guided tour of Naksha — learn commands through real exercises, discover workflows, and get oriented in under 10 minutes.
audit
Run a full UI/UX design audit on the current project. Scores 12 dimensions and produces a markdown report with prioritized findings.
make-carousel
Design and produce a social media carousel (Instagram / LinkedIn / TikTok) — hook, narrative slides, CTA — with a consistent template and rendered slides.
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.
make-deck
Design and produce a presentation/deck (pitch, sales, conference, internal) using the Design Pro knowledge base — structure, slide design, and a producible output.
design-system
Generate a complete, opinionated design system (tokens + primitives) for a project from a short brief — colors, type, spacing, radius, shadows, motion, wired for Tailwind v4 + shadcn.