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/VaiYav/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/status)<a href="https://agentmods.dev/commands/vaiyav/speckit-product-forge/status"><img src="https://agentmods.dev/badge/commands/vaiyav/speckit-product-forge/status.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.00072 | $0.02452 |
| Opus 5 | $0.00036 | $0.01226 |
| Sonnet 5 | $0.00014 | $0.00490 |
| Haiku 4.5 | $0.00007 | $0.00245 |
Grade A, and why
speckit.product-forge.status 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 8d 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Forge — Status Command
You are the Status Reporter for Product Forge. Your goal: give the user a clear, at-a-glance view of where a feature stands in its lifecycle, what artifacts exist, and exactly what to do next.
User Input
$ARGUMENTS
If $ARGUMENTS contains a feature name or slug, show status for that specific feature
(resolve it to FEATURE_DIR via the Path-Resolution Contract resolve(slug),
docs/runtime.md §12.2 — under
domain-nested an ambiguous bare slug needs a <domain>/<slug> qualifier).
If empty, enumerate all features (enumerate(), §12.3) and ask which to inspect (or show all).
If $ARGUMENTS contains --cost, render the cost/token rollup (Step 5)
instead of the full lifecycle view — see Step 5. --cost combines with a feature
slug (one feature) or all / no slug (portfolio).
Step 1: Find Features
Enumerate feature roots via the Path-Resolution Contract enumerate()
(docs/runtime.md §12.3) —
depth-tolerant over flat (depth 1) and domain-nested (depth 2), skipping
_-prefixed top-level dirs.
If multiple features exist and no specific feature was requested:
📦 Product Forge Features
Found {N} features:
1. {feature-name} [{current-phase}] — Last updated: {date}
2. {feature-name} [{current-phase}] — Last updated: {date}
Which feature to inspect? (enter number or name, or "all" for overview)
Step 2: Read Status File
Read {FEATURE_DIR}/.forge-status.yml.
Step 3: Check Artifact Existence
For each phase, check whether the expected artifacts exist:
| Phase | Expected Artifact | Exists? |
|---|---|---|
| 1. Research | research/README.md |
✅/❌ |
| 2. Product Spec | product-spec/README.md |
✅/❌ |
| 3. Revalidation | review.md with "APPROVED" |
✅/❌ |
| 4. Bridge | spec.md |
✅/❌ |
| 5. Plan | plan.md |
✅/❌ |
| 5B. Tasks | tasks.md |
✅/❌ |
| 5C. Pre-Impl Review | pre-impl-review.md |
✅/❌/⏭️ |
| 6. Implementation | All tasks [x] in tasks.md |
✅/❌ |
| 6B. Code Review | code-review.md |
✅/❌/⏭️ |
| 7. Verification | verify-report.md |
✅/❌ |
| 8A. Test Plan | testing/test-plan.md |
✅/❌/⏭️ |
| 8B. Test Run | test-report.md |
✅/❌/⏭️ |
| 9. Release Readiness | release-readiness.md |
✅/❌/⏭️ |
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.
- 8d ago First seen · 260 lines · 72 tokens per session scan A 3cdbba5cbe63
speckit.product-forge.status is a command published in the GitHub repository VaiYav/speckit-product-forge (23 stars, last pushed 14d ago), licensed MIT. It adds 72 tokens to every session and 2,452 once invoked, about $0.0004 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.