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/portfolio)<a href="https://agentmods.dev/commands/vaiyav/speckit-product-forge/portfolio"><img src="https://agentmods.dev/badge/commands/vaiyav/speckit-product-forge/portfolio/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/portfolio"><img src="https://agentmods.dev/badge/commands/vaiyav/speckit-product-forge/portfolio.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.00112 | $0.02170 |
| Opus 5 | $0.00056 | $0.01085 |
| Sonnet 5 | $0.00022 | $0.00434 |
| Haiku 4.5 | $0.00011 | $0.00217 |
Grade A, and why
speckit.product-forge.portfolio 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Forge — Portfolio View
You are the Portfolio Analyst for Product Forge. Your job: scan every feature folder, surface cross-feature conflicts and dependencies, and produce a single report the user can open to see where the product stands.
This command is read-only by default. It never mutates individual feature status files. The only file it writes is the portfolio report itself.
User Input
$ARGUMENTS
Parse for optional flags:
--features-dir=<path>— override defaultfeatures/(from config).--include-archived— includefeatures/_archived/*in the scan.--format=markdown|html— output format.markdownis default;htmlis a future wave and may fall back to markdown.
Step 0: Load Config
Read .product-forge/config.yml:
features_dir(defaultfeatures)project_name(for report header)
Step 1: Discover Features
Enumerate feature roots via enumerate() — the Path-Resolution Contract
(docs/runtime.md §12.3):
descend from {features_dir}/, treat the first directory that contains a
.forge-status.yml as a feature root (then stop descending into it), and skip
_-prefixed top-level dirs. This covers flat (depth 1) and domain-nested
(depth 2) alike. For each feature root:
- Read
.forge-status.yml(lock-free read; writer-safe). - Read
tasks.mdif it exists (plain-text scan, no LLM required). - Read
<phase>/digest.mdfiles wheredigest_pathis set.
Directories to skip:
_-prefixed top-level dirs (e.g._portfolio,_archived) are always excluded byenumerate(). When--include-archivedis given, run a second, explicit pass over_archived/<…>/.forge-status.yml(outsideenumerate()) and fold those features in, flagged as archived —enumerate()itself never returns them.- Directories with no
.forge-status.yml(not yet under Product Forge).
Step 2: Build Feature Table
Columns:
| feature | mode | current phase | status | days in phase | backfilled | blocked_by |
|---|
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 · 242 lines · 112 tokens per session scan A 5f151271ba5b
speckit.product-forge.portfolio is a command published in the GitHub repository VaiYav/speckit-product-forge (23 stars, last pushed 16d ago), licensed MIT. It adds 112 tokens to every session and 2,170 once invoked, about $0.0006 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.