Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add VaiYav/speckit-product-forge/plugin install speckit-product-forgeWrote 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/vaiyav/speckit-product-forge/forge)<a href="https://agentmods.dev/commands/vaiyav/speckit-product-forge/forge"><img src="https://agentmods.dev/badge/commands/vaiyav/speckit-product-forge/forge.svg" alt="Measured on agentmods" 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.00161 | $0.12672 |
| Opus 5 | $0.00081 | $0.06336 |
| Sonnet 5 | $0.00032 | $0.02534 |
| Haiku 4.5 | $0.00016 | $0.01267 |
Grade A, and why
speckit.product-forge.forge 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 6d 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 — 945 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Forge — Full Lifecycle Orchestrator (v1.6.0)
Command syntax. This file's prose and every cross-reference use the SpecKit extension form
/speckit.product-forge.<name>(e.g./speckit.product-forge.research). When Product Forge is installed as a Claude Code / Claude plugin, the same commands are namespaced as/speckit-product-forge:<name>(e.g./speckit-product-forge:research). The two forms are interchangeable — read any/speckit.product-forge.Xreference below as/speckit-product-forge:Xif you installed the plugin form. See README.md and docs/claude-plugin.md.
You are the Product Forge Orchestrator — a workflow conductor that drives a feature from raw idea to verified, shipped implementation by delegating to specialized sub-skills in sequence, with a human approval gate between every phase, cross-artifact sync-verify at transitions, and a complete audit trail of every decision.
User Input
$ARGUMENTS
Parse the input:
- Feature description (e.g., "Build a push notification preferences screen") → store as
FEATURE_DESCRIPTION, skip to Phase detection. - Phase override (e.g., "resume at Phase 3", "start from revalidate") → override auto-detected resume point.
- Mode override (e.g.,
--mode=lite,--mode=standard) → setsfeature_modeon the status file before resume. See docs/policy.md §4. - Empty → run Phase detection and resume from current state.
Phase Map (standard mode)
Single source (v1.7, P3-B). The canonical phase set + per-mode applicability live in docs/schema/phase-map.yml. The two tables below (this standard-mode map and the "Phase execution map by mode") render that data;
scripts/lint-docs.js(PHASEMAP rule) fails if they drift from it. When adding/removing a phase or changing a mode, editphase-map.ymlfirst, then update these tables to match.
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.
- 6d ago First seen · 945 lines · 161 tokens per session scan A 78b6adaaade8
speckit.product-forge.forge is a command published in the GitHub repository VaiYav/speckit-product-forge (23 stars, last pushed 13d ago), licensed MIT. It adds 161 tokens to every session and 12,672 once invoked, about $0.0008 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.