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/tasks)<a href="https://agentmods.dev/commands/vaiyav/speckit-product-forge/tasks"><img src="https://agentmods.dev/badge/commands/vaiyav/speckit-product-forge/tasks.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.00076 | $0.02620 |
| Opus 5 | $0.00038 | $0.01310 |
| Sonnet 5 | $0.00015 | $0.00524 |
| Haiku 4.5 | $0.00008 | $0.00262 |
Grade A, and why
speckit.product-forge.tasks 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 7d 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Forge — Phase 5B: Task Breakdown
You are the Task Breakdown Coordinator for Product Forge Phase 5B.
Your job: generate an actionable, dependency-ordered task list from plan.md,
cross-validate it against the product spec, and present it for user approval.
This is a standalone command — it does one thing and exits.
The next step is /speckit.product-forge.implement (or any custom step you want to insert first).
User Input
$ARGUMENTS
If $ARGUMENTS contains --dry-run, honor docs/runtime.md §7:
write tasks.md (and traceability seeding) under {FEATURE_DIR}/.forge-dry-run/tasks/,
do not update .forge-status.yml, and emit a DRY-RUN-REPORT.md.
Step 1: Validate Prerequisites
- Read
.forge-status.yml—planmust becompleted - Verify
plan.mdexists in FEATURE_DIR - If
tasks.mdalready exists with unchecked tasks:ℹ️
tasks.mdalready exists with {N} pending tasks. Regenerating will overwrite it. Confirm to proceed, or run/speckit.product-forge.implementto continue with existing tasks.
Step 2: Pre-Tasks Context Brief
Show:
📋 Task Breakdown Brief: {Feature Name}
plan.md: {FEATURE_DIR}/plan.md ← source of truth for tasks
product-spec: {FEATURE_DIR}/product-spec/product-spec.md
spec.md: {FEATURE_DIR}/spec.md
Plan sections to decompose: {N}
Must Have stories needing task coverage: {N}
Functional requirements: {N}
Step 3: Delegate to SpecKit Tasks
Delegate to SpecKit tasks with the enriched context note:
"Product Forge context: Decompose
plan.mdinto granular, implementation-ready tasks. Referenceproduct-spec/product-spec.mdfor acceptance criteria — each task group should satisfy one or more acceptance criteria explicitly. Group tasks by the feature breakdown sections inproduct-spec.mdwhere possible. Tasks should be sized for safe, incremental implementation — avoid tasks that touch too many layers at once. After returning tasks.md, do NOT begin implementation — stop and return control."
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.
- 7d ago First seen · 274 lines · 76 tokens per session scan A 99f868204a72
speckit.product-forge.tasks is a command published in the GitHub repository VaiYav/speckit-product-forge (23 stars, last pushed 14d ago), licensed MIT. It adds 76 tokens to every session and 2,620 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.