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/environment-setupgit 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/environment-setup)<a href="https://agentmods.dev/commands/imsaif/design-with-claude/environment-setup"><img src="https://agentmods.dev/badge/commands/imsaif/design-with-claude/environment-setup.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.00036 | $0.00769 |
| Opus 5 | $0.00018 | $0.00385 |
| Sonnet 5 | $0.00007 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
environment-setup 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 5d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Environment Variables Guide for designers. When invoked with $ARGUMENTS, you explain what environment variables are in plain language and guide the designer through setting them up correctly and safely.
What are environment variables (designer explanation)
"Imagine you have a Figma file with sensitive client information. You wouldn't share that file publicly. Environment variables work the same way — they're private settings (like API keys and passwords) that your app needs to run, stored separately from your code so they're never accidentally shared."
The three things to always know
- Never commit .env files to GitHub. API keys in public GitHub repos get stolen within minutes by automated bots.
- Each environment has its own .env file. Local development (.env.local), staging, and production all have different values.
- Environment variables are not automatic. You must restart your dev server after adding or changing them.
File naming conventions (Next.js)
.env.local— your local machine only, never committed.env.development— shared development values (no secrets).env.production— production values (set in Vercel dashboard, not in a file)
Step by step setup
Step 1 — Create your .env.local file
In your project root (same level as package.json):
touch .env.local
Or create it manually in your code editor.
Step 2 — Add your variables
NEXT_PUBLIC_SUPABASE_URL=https://yourproject.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=your-anon-key
STRIPE_SECRET_KEY=sk_test_yourkey
Step 3 — Understand the NEXT_PUBLIC_ prefix
- Variables starting with
NEXT_PUBLIC_are visible in the browser. - Variables WITHOUT this prefix are server-only (safer for secrets).
- Rule: API keys that are meant to be public (Supabase anon key, Stripe publishable key) get
NEXT_PUBLIC_. Secret keys (Stripe secret key, database passwords) do NOT.
Step 4 — Add .env.local to .gitignore
Open your .gitignore file and confirm this line exists:
.env.local
If it doesn't, add it. This tells Git to never track this file.
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.
- 5d ago First seen · 79 lines · 36 tokens per session scan A a140ae57f745
environment-setup is a command published in the GitHub repository imsaif/design-with-claude (11 stars, last pushed 14d ago), licensed MIT. It adds 36 tokens to every session and 769 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.
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.
colors
Run a color-only design audit — contrast, near-duplicates, dark mode, semantic coverage. Scoped variant of /ui-ux-suite:audit.
make-carousel
Design and produce a social media carousel (Instagram / LinkedIn / TikTok) — hook, narrative slides, CTA — with a consistent template and rendered slides.