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 brief-to-tasksgit 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/brief-to-tasks)<a href="https://agentmods.dev/skills/mshadmanrahman/claude-for-designers/brief-to-tasks"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/claude-for-designers/brief-to-tasks/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/brief-to-tasks"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/claude-for-designers/brief-to-tasks.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.00031 | $0.00384 |
| Opus 5 | $0.00015 | $0.00192 |
| Sonnet 5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
brief-to-tasks 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 breaking a design brief into executable work. Vague tasks produce vague output. Every task here must be completable by one person in one focused session.
Start by reading the design brief and the information architecture document if they exist. If neither exists, ask the user to complete /design-brief and /information-architecture first. Tasks cannot be accurate without this foundation.
Produce a task list with these four phases:
Phase 1: Foundation Tasks that must happen before screens can be built. Includes: design tokens (if not done), setting up the file structure, confirming the component library, documenting any existing patterns being reused.
Phase 2: Structure IA and wireframe tasks. Each screen in the inventory gets a wireframe task. Navigation flows get their own task. These are low-fidelity; the goal is structure, not polish.
Phase 3: Build High-fidelity screen and component tasks. One task per major screen or component. Include variant tasks separately (error state, empty state, responsive layout).
Phase 4: Review Critique, accessibility check, edge case review. These are not optional phases; list them as real tasks with time estimates.
For each task, include:
- A clear title starting with a verb (Design, Write, Build, Review, Define)
- A "done when" definition: the specific condition that marks this task complete
- Dependencies: which prior tasks must be complete before this one starts
Format as a markdown checklist. Show dependencies inline as "(requires: Task X)". Order tasks within each phase by dependency, not by importance. A task with no dependencies can run in parallel with others; call that out explicitly.
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 · 30 lines · 31 tokens per session scan A bc92a8849209
brief-to-tasks is a skill published in the GitHub repository mshadmanrahman/claude-for-designers (28 stars, last pushed 20d ago), licensed MIT. It adds 31 tokens to every session and 384 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
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
case-interview-practice
Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.