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/scolladon/craftWrote 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/agents/scolladon/craft/designer)<a href="https://agentmods.dev/agents/scolladon/craft/designer"><img src="https://agentmods.dev/badge/agents/scolladon/craft/designer/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/agents/scolladon/craft/designer"><img src="https://agentmods.dev/badge/agents/scolladon/craft/designer.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.00040 | $0.00246 |
| Opus 5.5 | $0.00016 | $0.00098 |
| Sonnet 5.5 | $0.00008 | $0.00049 |
| Haiku 4.5 | $0.00004 | $0.00025 |
Grade A, and why
designer 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 29d 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 write the design document for a feature. Your invocation carries: the resolved brief, the absolute working directory (work ONLY there), the design-doc output path, the template to fill, and any repo-specific context block — treat that block as binding constraints.
Contract:
- Read the repo's existing design docs, ADRs, and the code patterns the feature must follow BEFORE designing. Design within the house style, not beside it.
- When external behaviour must be matched (another tool, a wire format, a spec), pin it empirically — run the real thing in a controlled environment and record the pinned matrix in the doc. Never design from memory of an external system.
- Commit the doc with the conventional-commit message your invocation names.
- Final message: the doc path + the decision-candidates list, nothing else.
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.
- 29d ago Changed · +1 lines 417a1987a225
- 1mo ago First seen · 21 lines · 40 tokens per session scan A d591f410f39d
designer is an agent published in the GitHub repository scolladon/craft (2 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 246 once invoked, about $0.0002 per session on Opus 5.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-31.
Other agents, from other repositories
design-advisor
Use after architect, before/parallel to pm, for any UI-bearing feature (landing pages, dashboards, admin panels, web apps, React Native apps). Picks a design system, enumerates the component inventory, writes text-form wireframes, and locks the a11y + responsive + (mobile) platform-integration contract. Outputs…
unfolding-ux-designer
UX Designer role in the Unfolding Specs process. Acts as the user's advocate — challenges the Feature spec from a usability perspective, collaborates with the PO to refine assumptions, and designs tech-agnostic user experience components (interaction flows, states, component hierarchy). Commissioned by the PO for…
unfolding-ui-expert
UI Expert role in the Unfolding Specs process. Maps tech-agnostic UX components to concrete technology (CSS framework, interaction library, HTML structure). Commissioned by the Architect when a UX component has no mapping or the mapping is non-trivial.
designer
A planning agent that proposes user-interface and user-experience guidelines for a feature. It compares Japanese and Western design patterns for a specified audience and interface area, such as a form, dashboard, or landing page.
usability-reviewer
A usability reviewer that checks how an interface feels and works for people, including accessibility, navigation, consistency, and error handling. It returns a blocking score and categorized issues.
build
Build phase agent — implements sub-tasks sequentially using TDD.