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 skills add mshadmanrahman/claude-for-designers --skill design-briefgit clone --depth 1 https://github.com/mshadmanrahman/claude-for-designersWrote 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/skills/mshadmanrahman/claude-for-designers/design-brief)<a href="https://agentmods.dev/skills/mshadmanrahman/claude-for-designers/design-brief"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/claude-for-designers/design-brief/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/skills/mshadmanrahman/claude-for-designers/design-brief"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/claude-for-designers/design-brief.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.00034 | $0.00407 |
| Opus 5 | $0.00017 | $0.00204 |
| Sonnet 5 | $0.00007 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
design-brief 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 12d 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.
What it actually says
You are writing a design brief. This is the single source of truth for the project. Everything that comes after this step references it.
First, ask the following if no Requirements Handshake exists from /grill-me:
- What is the product or feature being designed?
- Who are the primary users?
- What emotions should the design evoke when a user succeeds at their task?
- What does "done" look like for this project?
Ask these one at a time, and offer a suggested answer with each so a student who is unsure can accept or refine it rather than stall on a blank.
If a Requirements Handshake exists from /grill-me, pull the confirmed constraints directly into the brief. Do not re-ask questions that are already answered there.
Then generate a brief with these six sections:
1. Project context What is being built and why now. One paragraph. No vague mission statements.
2. Target user Who this is for. Name a specific person or role, not a demographic range. Include what they care about and what they do not.
3. Emotional tone and design direction The specific emotion the design should produce. Not "clean and modern." Name the actual feeling: confidence, calm, urgency, delight. Then name one reference product that nails that feeling and why.
4. Functional requirements What the design must do. Numbered list. Each item starts with a verb.
5. Constraints What cannot change. Platform, tech stack, existing components, accessibility requirements, legal limits.
6. Success criteria How you will know this worked. Measurable where possible. At minimum: one behavioral signal and one metric.
Be specific throughout. If you cannot be specific, flag it as an open question rather than filling in with vague language.
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.
- 12d ago First seen · 39 lines · 34 tokens per session scan A 7f9a5be7c6d2
design-brief is a skill published in the GitHub repository mshadmanrahman/claude-for-designers (28 stars, last pushed 20d ago), licensed MIT. It adds 34 tokens to every session and 407 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 skills, from other repositories
brand-identity
Brand strategy and identity design for businesses and products. Use when creating brand guidelines, developing visual identity systems, or defining brand positioning.
graphic-design
Professional graphic design principles for digital and print media. Use when creating visual designs, choosing color palettes, typography, layouts, or providing design feedback.
generic-react-ux-designer
Professional UI/UX design expertise for React applications. Covers design thinking, user psychology (Hick's/Fitts's/Jakob's Law), visual hierarchy, interaction patterns, accessibility, performance-driven design, and design critique. Use when designing features, improving UX, solving user problems, or conducting design…
frontend-enhancer
This skill should be used when enhancing the visual design and aesthetics of web applications. It provides modern UI components, design patterns, color palettes, animations, and layout templates. REQUIRES ui-research skill first. Use this skill for tasks like improving styling, creating responsive designs…
generic-design-system
Complete design system reference for any project - colors, typography, spacing, components, animations. Adapts to project theme and tech stack. Use when implementing UI, choosing colors, creating animations, or ensuring brand consistency. For new design systems, use ui-research skill first.
generic-ux-designer
Professional UX expertise for any project type. Covers user research, design thinking, interaction patterns, accessibility, and design critique. Use when designing new features, improving UX, conducting design reviews, or evaluating user flows. For visual UI work, combine with ui-research skill.