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.not-greenWrote 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.not-green)<a href="https://agentmods.dev/commands/arrrrny/zuraffa/speckit.spec-stats.not-green"><img src="https://agentmods.dev/badge/commands/arrrrny/zuraffa/speckit.spec-stats.not-green/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.not-green"><img src="https://agentmods.dev/badge/commands/arrrrny/zuraffa/speckit.spec-stats.not-green.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.00034 | $0.00205 |
| Opus 5 | $0.00017 | $0.00102 |
| Sonnet 5 | $0.00007 | $0.00041 |
| Haiku 4.5 | $0.00003 | $0.00020 |
Grade A, and why
speckit.spec-stats.not-green 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
Spec Stats — Not Green
Show specs whose TDD state is not green — a TDD list exists but no behavior has reached DONE (or the suite is red).
User Input
$ARGUMENTS
Optional flags:
--json— machine-readable output
Execution
node .specify/extensions/spec-stats/scripts/spec-stats.mjs not-green
The engine scans each feature with a tdd/test-list.md and reports those with zero DONE behaviors, quoting the loop mode (full / outer-only / inside-out) so the user knows whether the inner loop was ever derived. For red-suite evidence, point the user at the feature's tdd/cycle-log.md. Read-only.
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 · 25 lines · 34 tokens per session scan A 6a40b9f8f1e7
speckit.spec-stats.not-green is a command published in the GitHub repository arrrrny/zuraffa (5 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 205 once invoked, about $0.0002 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-09-03.
Other commands, from other repositories
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, evidence, and PR-ready output.
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
fix
Correction automatisee des bugs identifies par la QA Recette.
hatch3r-bug-pipeline
Run a known-cause bug fix through a 3-phase test-first pipeline -- reproduce + root-cause, regression-test + fix together, then root-cause-depth review -- with full sub-agent delegation.
feature-implement-execute
Phase 4 of develop: Execute the implementation plan with per-task TDD, quality gates, and completion verification.
ralph.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.