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/michael-fay/speckit-parallel-agentsWrote 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/michael-fay/speckit-parallel-agents/speckit.analyze)<a href="https://agentmods.dev/commands/michael-fay/speckit-parallel-agents/speckit.analyze"><img src="https://agentmods.dev/badge/commands/michael-fay/speckit-parallel-agents/speckit.analyze/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/michael-fay/speckit-parallel-agents/speckit.analyze"><img src="https://agentmods.dev/badge/commands/michael-fay/speckit-parallel-agents/speckit.analyze.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.00029 | $0.03632 |
| Opus 5 | $0.00015 | $0.01816 |
| Sonnet 5 | $0.00006 | $0.00726 |
| Haiku 4.5 | $0.00003 | $0.00363 |
Grade A, and why
speckit.analyze 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 439 lines · 29 tokens per session scan A 99dcbabcf325
speckit.analyze is a command published in the GitHub repository michael-fay/speckit-parallel-agents (2 stars, last pushed 3mo ago), with no licence file. It adds 29 tokens to every session and 3,632 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
deepen
Spare-budget design pass. Make one shallow module deep — smaller interface, behavior held, tests green before & after.
review
Adversarial senior review of the spec before build. Refute, don't rubber-stamp. Ends in a go/no-go gate.
check
Drift detector. Diff SPEC.md against code. Read-only, zero writes.
build
Plan-then-execute against SPEC.md. Native Claude Code loop, no sub-agents.
speckit.companion.living-coverage
Report living-spec requirement→test coverage — per requirement, whether its coverage tier maps a test (opt-in, read-only, never halts).
autospec.analyze
Analyze cross-artifact consistency and quality in YAML format.