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/genai-jerry/claude-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/genai-jerry/claude-software-factory/fasttrack)<a href="https://agentmods.dev/commands/genai-jerry/claude-software-factory/fasttrack"><img src="https://agentmods.dev/badge/commands/genai-jerry/claude-software-factory/fasttrack/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/genai-jerry/claude-software-factory/fasttrack"><img src="https://agentmods.dev/badge/commands/genai-jerry/claude-software-factory/fasttrack.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.00021 | $0.01620 |
| Opus 5 | $0.00010 | $0.00810 |
| Sonnet 5 | $0.00004 | $0.00324 |
| Haiku 4.5 | $0.00002 | $0.00162 |
Grade A, and why
fasttrack 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 9d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Fast-Track Engineer of the Software Factory (see FACTORY.md).
Input: an issue labelled factory:fast-track: $ARGUMENTS
Step 0 — load the repo profile
Read .factory/profile.json at the repository root. It is the authoritative
source for this repo's stack, branches, commands (test/build/lint),
conventions, qa_notes and gotchas. Everything below refers to those
values. If the file is missing or unparseable: stop, comment on the issue,
apply factory:blocked — a factory repo must have a profile.
Step 0a — resolve the integration branch
The fast lane skips the ceremony, not the staging step. Its PR lands on the
org's integration branch, and reaches branches.default only through a
promotion PR (FACTORY.md §6a). The epic-branch layer (§6b, the policy's
epics key) never applies here: a fast-track change has no epic and no epic
branch, under either policy value. Resolve the integration branch before you
branch:
- Read
.github/factory-branches.json, the org's staging policy. Treat a missing file as{"staging": "staging", "required": true, "auto_create": true}. - The branch's name is the profile's
branches.stagingwhen that is a non-null string, else the policy'sstaging. - The step is required unless the policy sets
required: false.- Required: base your PR on that branch, never on
branches.default. If it does not exist on the remote and the policy'sauto_createis notfalse, cut it frombranches.default(git push origin origin/<default>:refs/heads/<integration>) and say so in the PR body. Ifauto_createisfalseand the branch is missing: stop, comment naming the branch that has to exist, applyfactory:blocked. required: false: the pre-policy fallback — the profile'sbranches.stagingwhen it names one, elsebranches.default.
- Required: base your PR on that branch, never on
Call the result the integration branch below.
Mission
Fast-track is the lane for a change too small to be worth OpenSpec ceremony: no spec, no design, no task breakdown, no gates. Skipping the ceremony does not mean skipping the work. Do the whole thing in this one run — read the issue, make the change, prove it, open a PR — and leave a human nothing to do but review and merge.
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.
- 9d ago First seen · 118 lines · 21 tokens per session scan A 1e6db709b6ca
fasttrack is a command published in the GitHub repository genai-jerry/claude-software-factory (2 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 1,620 once invoked, about $0.0001 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-31.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
handoff
Export a Waybill Bundle by default, or import one when requested.