Borrowing it
Nothing to install: this file belongs to girishr/SpecPilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/girishr/SpecPilot/main/.claude/commands/specpilot-report.mdgit clone --depth 1 https://github.com/girishr/SpecPilotWrote 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/girishr/specpilot/specpilot-report)<a href="https://agentmods.dev/commands/girishr/specpilot/specpilot-report"><img src="https://agentmods.dev/badge/commands/girishr/specpilot/specpilot-report.svg" alt="Measured on agentmods" 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.00282 |
| Opus 5 | $0.00010 | $0.00141 |
| Sonnet 5 | $0.00004 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
specpilot-report 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 8d 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
Formalize the Spec-First review gate (mandate 8) for the pending change.
- Classify the pending change as trivial, feature, or architectural:
- Trivial: no spec update required.
- Feature: touches
project/requirements.mdandplanning/tasks.md. - Architectural: touches all affected spec files plus
CHANGELOG.md.
- Read the relevant
.specs/files per the Context routing table (session start →project/project.yaml; feature/bug → +project/requirements.md,planning/tasks.md; architecture → +architecture/architecture.md; tests → +quality/tests.md; security → +security/threat-model.md,security/security-decisions.md; planning → +planning/tasks.md,planning/roadmap.md). - Update the affected spec files first — before writing any code.
- Present a Spec Report: classification, files touched, what changed in each, and what the specs now say.
- Wait for the user's literal
yes, proceedbefore writing or editing any code or non-spec file. An ambiguous "ok" or "sure" is not sufficient for an architectural-tier change — ask for the explicit phrase if it wasn't given.
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.
- 8d ago First seen · 14 lines · 0 tokens per session scan A ba699b927c96
specpilot-report is a command published in the GitHub repository girishr/SpecPilot (37 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 282 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-30.
Other commands, from other repositories
ensemble:generate-project-router-rules
Generate project-specific router rules by analyzing the project's tech stack.
ensemble:generate-router-rules
Generate router rules by introspecting installed agents and skills.
speckit.spec-stats.open
On-demand view of everything not complete: what stage each is stuck at, what the immediate next artifact/command is, oldest-untouched first, stale warnings past staleafterdays.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
scout-scan
Scan a path with Scout and walk through the security findings.
init
Birth or wake your homunculus.