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 agentmods add commands/zxpmail/reqforge/product-spec-buildergit clone --depth 1 https://github.com/zxpmail/ReqForgeWhat 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 | $0.00012 | $0.00392 |
| Opus 5 | $0.00006 | $0.00196 |
| Sonnet 5 | $0.00002 | $0.00078 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
product-spec-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 3d 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: /product-spec-builder
Entry: /product-spec-builder or describe product idea. Full workflow → SKILL.md.
Mode routing (read one workflow ref)
| Mode | Trigger | Read |
|---|---|---|
| Quick | one sentence / "quick" / "fast" | references/workflow-quick-mode.md only |
| Distillation | distill / 蒸馏 / infer what I need | references/distillation-mode.md |
| Light Grill | grill me / 烤问 / stress-test | references/light-grill-mode.md |
| 0-to-1 | no Spec yet, full deep-dive | references/workflow-0-to-1.md |
| Iteration | Product-Spec.md exists | references/workflow-iteration.md |
Startup routing → references/startup-check.md.
Phases (index)
| Phase | Reference | Acceptance |
|---|---|---|
| Discovery | workflow-0-to-1 | One-paragraph concept agreed |
| Detail / Interview | conversation-strategy | Spec sections fillable without guessing |
| Distillation | distillation-mode | 4-path inference + cross-validation; Distillation Map (✅/⚠️/❓); ❓ feeds 0-to-1/Quick clarifying questions |
| Critique Gate | critique-gate | Three structural signals scanned; findings resolved or marked [TBD] |
| Spec write | product-spec-template | Product-Spec.md confirmed (HARD-GATE lifts only after explicit user confirm) |
| Iteration | workflow-iteration | Major/minor → edit Spec; moderate scoped feature → /change-manager propose |
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.
- 3d ago First seen · 32 lines · 12 tokens per session scan A 8504064bc920
product-spec-builder is a command published in the GitHub repository zxpmail/ReqForge (18 stars, last pushed 13d ago), licensed MIT. It adds 12 tokens to every session and 392 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-30.
Other commands, from other repositories
meta-theory
Run the MetaKim meta-theory governance dispatcher.
cross-critique
Adversarial multi-angle critique. All three auditors fire in parallel (codex=technical, gemini=strategic, claude=ux). Counter-args ranked by rebuttal survival score, not raw severity. Usage: /cross-critique [--with | list | compare].
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
ijfw
IJFW command index. Groups commands by intent: Build / Remember / Ship / Review / Configure.
ijfw-execute
Jump directly to the IJFW workflow Execute phase (Deep D4 / Quick Q3). Usage: /ijfw-execute [task or phase name].
core-review
Review code changes against SpecOps project-specific patterns. Catches recurring failure modes from real PRs — tool abstraction violations, generated file drift, cross-platform gaps, variable inconsistencies, and more. Complements full-review-gate (generic quality) and pr-fix (applying bot comments).