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/Kripu77/software-factoryWrote 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/kripu77/software-factory/lead)<a href="https://agentmods.dev/commands/kripu77/software-factory/lead"><img src="https://agentmods.dev/badge/commands/kripu77/software-factory/lead/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/kripu77/software-factory/lead"><img src="https://agentmods.dev/badge/commands/kripu77/software-factory/lead.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.00000 | $0.00169 |
| Opus 5.5 | $0.00000 | $0.00068 |
| Sonnet 5.5 | $0.00000 | $0.00034 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
lead 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 1mo 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.
What it actually says
Read lanes/tech-lead.md and AGENTS.md. Follow /to-tickets. Ask Telemetry when production data exists. Do not implement. Do not merge.
At start, factory.sh mem read for this issue (or project if no issue). Empty memory is fine. Memory is a hint. GitHub is the source of truth when this laptop has no rows.
After tickets exist, start factory.sh floor (or one factory.sh lane). Dispatch is factory.sh only. Implementing, reviewing, or watching CI in this session is a failed run. Cursor is a floor door, not a factory.sh --runner, unless a Cursor CLI exists. Workers use --runner on PATH.
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.
- 1mo ago First seen · 11 lines · 0 tokens per session scan A d9f500e04ccc
lead is a command published in the GitHub repository Kripu77/software-factory (7 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 169 tokens. 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-31.
Other commands, from other repositories
feedback
File a structured feedback entry when a downstream stage discovers an upstream .forge/ artifact needs revision.
spec
Create a PRD via interview and codebase exploration, output as .forge/prd.md.
triage
Promote ideas from Ideas.md into Epics or User Stories in the Epic backlog (dedup, typed ID, voice).
triage-bug
Turn bug Inbox reports into registered, prioritized bugs (separate from /triage).
init-ledger
(Ledger) Create the ledger repository — Registry + Config — the one-time setup.
bug
Report a bug instantly to the bug Inbox (append-only, any language, safe mid-work).