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/ethanaubuchon/dossier-tradecraftWrote 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/ethanaubuchon/dossier-tradecraft/design)<a href="https://agentmods.dev/commands/ethanaubuchon/dossier-tradecraft/design"><img src="https://agentmods.dev/badge/commands/ethanaubuchon/dossier-tradecraft/design/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/commands/ethanaubuchon/dossier-tradecraft/design"><img src="https://agentmods.dev/badge/commands/ethanaubuchon/dossier-tradecraft/design.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.00029 | $0.02192 |
| Opus 5 | $0.00015 | $0.01096 |
| Sonnet 5 | $0.00006 | $0.00438 |
| Haiku 4.5 | $0.00003 | $0.00219 |
Grade A, and why
design 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 11d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are starting a /design session. The topic (if provided): $ARGUMENTS
This is the /design recipe of the dossier-tradecraft framework — early-stage design exploration for settling the shape of a feature/recipe/system before its implementation gets scoped.
Principles
- Vault is the home. The design note lives in the vault as long-lived rationale across many sessions. If we're in a repo, that's additive context — not a different destination.
- Re-entry is typical. Most invocations refine an existing design note rather than creating a new one. Search by tag (
design) + topic, not by path. - Required structural element: an
## Approachsection. Forces synthesis posture; prevents option-collection-without-decision. Other sections are agent-driven per topic. - Holistic refinement, not Unknowns walk. Design iteration touches intertwined elements (architecture, components, data flow). EXISTING-DESIGN mode presents a summary and invites refinement — no checklist to walk.
- Agent-judged writes. Decide slug, structure, and edits directly; surface what was done so the user can redirect post-hoc. No propose-then-approve gates.
- Inline integration. Findings during the session land in the design note itself, including those from inline research methodology (see Step 4.c). Research is methodology used inside this recipe, not a separate destination — there's no standalone research-note kickback.
- Loop exits on natural signal. No 3-option decision matrix at every cycle.
Workflow
-
Load context. Invoke the
load-contextskill (vault grounding: profile, inbox check, project area pre-warm). If the working directory is inside a git repo, also note the cwd, current branch, and whether a project agent-instruction file (CLAUDE.md, AGENTS.md, etc.) is present. -
Resolve design doc. Search the vault for an existing design note on this topic.
- Use
mcp__dossier-mcp__search_noteswith the topic terms; filter fortag:designif the search supports it, otherwise check thetagsfield on each candidate. - 1 match → call
mcp__dossier-mcp__get_noteto load it, enter EXISTING-DESIGN MODE. - >1 match → list candidates briefly (slug + title) and ask the user which to continue with.
- 0 matches → before writing, surface "no existing design note found for this topic, creating a new one" so the user can redirect if they expected a match. Then enter NEW-DESIGN MODE.
- Use
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.
- 11d ago First seen · 106 lines · 29 tokens per session scan A ff160452686f
design is a command published in the GitHub repository ethanaubuchon/dossier-tradecraft (3 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 2,192 once invoked, about $0.0001 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-31.
Other commands, from other repositories
color-palette
Generate an accessible colour palette from a hex value.
ux-extract
Exhaustively extract UX patterns from a reference web app into a reusable pattern library.
summary
Generate a consolidated project brief from design artifacts. For the full spec package with YAML specs and validation, use /compile instead.
p3-ux-wireframes
Creates wireframes (ASCII art) for the most important screens with interaction descriptions.
bmad-agent-ux-designer
UX designer and UI specialist. Use when the user asks to talk to Sally or requests the UX designer.
design-review
Structured design review of the current build or a URL — hierarchy, consistency, taste, polish.