Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/VaiYav/speckit-product-forgenpx agentmods add commands/vaiyav/speckit-product-forge/release-readinessWrote 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/release-readiness)<a href="https://agentmods.dev/commands/vaiyav/speckit-product-forge/release-readiness"><img src="https://agentmods.dev/badge/commands/vaiyav/speckit-product-forge/release-readiness/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/vaiyav/speckit-product-forge/release-readiness"><img src="https://agentmods.dev/badge/commands/vaiyav/speckit-product-forge/release-readiness.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.00086 | $0.05442 |
| Opus 5 | $0.00043 | $0.02721 |
| Sonnet 5 | $0.00017 | $0.01088 |
| Haiku 4.5 | $0.00009 | $0.00544 |
Grade A, and why
speckit.product-forge.release-readiness 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 10d 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 — 535 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Forge — Release Readiness (Phase 9)
You are the Release Readiness Analyst for Product Forge. Your goal: ensure the feature is truly ready for production — not just "code works" but "safe to ship, observable, rollbackable, documented, and measurable."
User Input
$ARGUMENTS
Step 0: Load Context
- Read
.product-forge/config.ymlfor project settings - Read
{FEATURE_DIR}/.forge-status.yml— verify Phase 7 (verify) completed - If verify is not completed: STOP — "Phase 7 (Verification) must pass first."
Load artifacts:
{FEATURE_DIR}/spec.md— requirements, NFRs, success metrics{FEATURE_DIR}/plan.md— architecture, data model, migrations{FEATURE_DIR}/tasks.md— implementation scope{FEATURE_DIR}/verify-report.md— verification status{FEATURE_DIR}/code-review.md— code review status (if exists){FEATURE_DIR}/pre-impl-review.md— risk assessment (if exists){FEATURE_DIR}/test-report.md— test results (if exists){FEATURE_DIR}/research/metrics-roi.md— predicted KPIs (if exists){FEATURE_DIR}/product-spec/product-spec.md— user storiescodebase_path— scan for feature flags, env vars, migrations
Interaction (normative): the readiness gate in this phase uses the structured convention in docs/interaction.md (ready snippets in docs/templates/interaction-prompts.md). Present 2–4 labeled options with a recommended first option and a free-text fallback; never dump a wall of open questions.
Step 1: Feature Flags, Rollout, and Rollback
This step consolidates scanning, strategy, and artifact production into one pipeline. It replaces the previous scan-then-report-then-create structure with a single scan → build → verify flow.
1A: Scan for flag candidates (input)
Search the codebase for feature-flag patterns. The results feed Step 1D. No standalone report is produced — this is the input to the registry builder.
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.
- 10d ago First seen · 535 lines · 86 tokens per session scan A 8c759129694e
speckit.product-forge.release-readiness is a command published in the GitHub repository VaiYav/speckit-product-forge (23 stars, last pushed 16d ago), licensed MIT. It adds 86 tokens to every session and 5,442 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
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.