Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/arrrrny/zuraffanpx agentmods add commands/arrrrny/zuraffa/speckit.spec-stats.reportWrote 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/arrrrny/zuraffa/speckit.spec-stats.report)<a href="https://agentmods.dev/commands/arrrrny/zuraffa/speckit.spec-stats.report"><img src="https://agentmods.dev/badge/commands/arrrrny/zuraffa/speckit.spec-stats.report/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/arrrrny/zuraffa/speckit.spec-stats.report"><img src="https://agentmods.dev/badge/commands/arrrrny/zuraffa/speckit.spec-stats.report.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.00070 | $0.00522 |
| Opus 5.5 | $0.00028 | $0.00209 |
| Sonnet 5.5 | $0.00014 | $0.00104 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
speckit.spec-stats.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 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
Spec Stats — Report
Generate the spec portfolio dashboard for the current project.
User Input
$ARGUMENTS
Optional flags:
--json— print the machine-readablestats.jsonto stdout (no files written)--out <path>— write the markdown dashboard to this path (overrides configoutput_path)--render --in <stats.json>— render an existing snapshot instead of re-scanning
Execution
Run the bundled Node engine from the repository root:
node .specify/extensions/spec-stats/scripts/spec-stats.mjs report
# or: node .specify/extensions/spec-stats/scripts/spec-stats.mjs report --json
# or: node .specify/extensions/spec-stats/scripts/spec-stats.mjs report --out /tmp/stats.md
The engine:
- Lists every
specs/<NNN>-<slug>/directory. - Detects each feature's stage (
specified → planned → tasked → implementing → complete) from file presence andtasks.mdcheckbox counts. - Detects whether the TDD extension is installed in this project (
.specify/memory/tdd-profile.mdor.specify/extensions/tdd). When installed, it reads each feature'stdd/test-list.mdand renders the TDD Deep Stats table with columns:#,feature,A(acceptance behaviors),U(unit behaviors),char(characterization behaviors),DONE(behaviors inDONEstate),loop(full/outer-only/inside-out/absent), andtasks.md(updatedwhen TDD markers are present, elseabsent), plus a totals row. - Writes the dashboard to
output_path(default.specify/stats/SPEC-STATS.md) and astats.jsonsnapshot beside it.
Report the output path (or the JSON) back to the user. This command is read-only — it never modifies specs, tasks, or code.
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 · 37 lines · 70 tokens per session scan A 04283e8dc8ae
speckit.spec-stats.report is a command published in the GitHub repository arrrrny/zuraffa (5 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 522 once invoked, about $0.0003 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-09-03.
Other commands, from other repositories
sdlc
Route a task to the next synced SDLC workflow based on current artifacts and repo state.
validate-product
Validate critical product assumptions and hypotheses through bounded experiment design, precommitted thresholds, and host authorization gates.
sprint
Équipe de Développement Sprint - Implémentation parallèle de stories utilisant les Agent Teams.
workflow-design
Exécuter la phase de Conception (Solutioning) - spécification technique et architecture.
daily-standup
Génération Résumé Daily Stand-up.
plan
PM planning workflow that gathers requirements, decomposes them into prioritized tasks, defines API contracts, and produces both a machine-readable plan and a human-readable tracker in docs/plans/.