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/qa)<a href="https://agentmods.dev/commands/kripu77/software-factory/qa"><img src="https://agentmods.dev/badge/commands/kripu77/software-factory/qa/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/qa"><img src="https://agentmods.dev/badge/commands/kripu77/software-factory/qa.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.00022 | $0.00207 |
| Opus 5.5 | $0.00009 | $0.00083 |
| Sonnet 5.5 | $0.00004 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
qa 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/qa.md and AGENTS.md. Prefer /run-smoke-tests when a suite exists. Otherwise /browser-use. Report findings. Do not implement. Do not merge.
At start, factory.sh mem read for this issue or PR. Write started only if none in progress: factory.sh mem write --lane qa --status started --harness <claude|cursor|codex|grok> --issue . At the end, factory.sh mem write --lane qa --status done|blocked|failed --harness <claude|cursor|codex|grok> --issue --summary "" --evidence --next-steps "". That write comments on the GitHub issue. started does not. Missing memory or a comment failure: warn once and continue.
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 · 9 lines · 22 tokens per session scan A 9435c6ea77d5
qa is a command published in the GitHub repository Kripu77/software-factory (7 stars, last pushed 28d ago), licensed MIT. It adds 22 tokens to every session and 207 once invoked, about $0.0001 per session on Opus 5.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
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
recette
Tests d'acceptance automatises avec Claude in Chrome.
cover
Generate tests that do not exist yet. Analyzes coverage gaps, then writes and runs new test files across three tiers (unit, integration via testcontainers, Playwright E2E), one test-generator agent per tier, healing failures for up to 3 iterations. Use when code has no tests or when raising coverage after…
ia-test-browser
Run browser tests on pages affected by current PR or branch.
lavra-qa
Browser-based QA verification of the running app -- systematic testing from the user's perspective.