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/zxpmail/ReqForgeWrote 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/zxpmail/reqforge/design-brief-builder)<a href="https://agentmods.dev/commands/zxpmail/reqforge/design-brief-builder"><img src="https://agentmods.dev/badge/commands/zxpmail/reqforge/design-brief-builder/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/zxpmail/reqforge/design-brief-builder"><img src="https://agentmods.dev/badge/commands/zxpmail/reqforge/design-brief-builder.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.00009 | $0.00166 |
| Opus 5.5 | $0.00004 | $0.00066 |
| Sonnet 5.5 | $0.00002 | $0.00033 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
design-brief-builder 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 1mo 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
Command: /design-brief-builder
Entry: /design-brief-builder. Prereq: Product-Spec.md. Full workflow → references/workflow.md.
| Phase | Reference | Acceptance |
|---|---|---|
| Startup | workflow.md § Startup | Questionnaire + Spec loaded |
| Interview | interview-dimension-checklist + strategies | Sufficiency Must Meet |
| Translation | workflow.md § Translation | User confirms direction |
| Output | anti-ai-slop + template | Design-Brief.md confirmed |
| Next Step Gate | next-step-gate.md | User chose A/B/C; .forge/design-next-step.json or /design-maker invoked |
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.
- 1mo ago First seen · 17 lines · 9 tokens per session scan A faad5642914d
design-brief-builder is a command published in the GitHub repository zxpmail/ReqForge (18 stars, last pushed 15d ago), licensed MIT. It adds 9 tokens to every session and 166 once invoked, about $0.0000 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-30.
Other commands, from other repositories
design-bootstrap
Bootstrap a design system from a Figma file via MCP: extract token variables, identify components, scaffold foundation docs and a component inventory. Use when starting a new project with a Figma file. Do not use when docs exist or there is no Figma file.
atom-audit-fleet
Audit every atom in parallel against the component guidelines, one worker per small group, merging rows into one ATOMAUDIT.md table (orchestrator-workers variant of atom-audit). Use when the atom count is 6 or more and COMPONENTGUIDELINES.md exists. Do not use below 6 atoms (use atom-audit single-agent), without…
mcp-server-vet
Read-only inspection of a third-party MCP server BEFORE it is added or trusted: scans tool descriptions and scopes for poisoning, returns an add, decline or sandbox verdict for a human. Never installs. Do not use to vet a skill or plugin (use skill-vet), to review first-party code (use review-hard or security-review)…
screen-spec-fleet
Generate one spec document per screen in parallel from Figma frames, one worker per screen, merging SCREENMAP.md and routes.md from their partials; the orchestrator-workers variant of screen-spec. Use when the screen count is 6 or more, a Figma MCP is reachable, and foundations plus SCREENMAP exist. Do not use for a…
image-to-spec
Generate a design-system spec from an image (screenshot, mockup, or app screen) when there is no Figma source: a component spec (--component) or screen spec (--screen), auto-detected. A gated --gameplay mode (off by default) derives a game MECHANICSSPEC.md from screenshots and playtest notes. Use when you have only an…
atom-audit
Produce ATOMAUDIT.md table auditing every atom component against COMPONENTGUIDELINES.md (memo, callbacks, inline styles, touch target, a11y, reduced motion). Use when 2-4 weeks have passed since last audit, 5+ new atoms shipped, or COMPONENTGUIDELINES has a new normative rule. Do not use when no atoms exist (run…