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 skills/arrrrny/zuraffa/speckit-spec-stats-openWrote 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/skills/arrrrny/zuraffa/speckit-spec-stats-open)<a href="https://agentmods.dev/skills/arrrrny/zuraffa/speckit-spec-stats-open"><img src="https://agentmods.dev/badge/skills/arrrrny/zuraffa/speckit-spec-stats-open/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/skills/arrrrny/zuraffa/speckit-spec-stats-open"><img src="https://agentmods.dev/badge/skills/arrrrny/zuraffa/speckit-spec-stats-open.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.00044 | $0.00262 |
| Opus 5.5 | $0.00018 | $0.00105 |
| Sonnet 5.5 | $0.00009 | $0.00052 |
| Haiku 4.5 | $0.00004 | $0.00026 |
Grade A, and why
speckit-spec-stats-open 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 Open Skill
Spec Stats — Open
Show every spec that is not complete, oldest-untouched first, with stale warnings.
User Input
$ARGUMENTS
Optional flags:
--stale-after <days>— override configstale_after_days(default 14)--json— machine-readable output
Execution
node .specify/extensions/spec-stats/scripts/spec-stats.mjs open
# or: node .specify/extensions/spec-stats/scripts/spec-stats.mjs open --stale-after 7
The engine lists each incomplete feature with its current stage, progress (checked/total), last-updated date, and a ⚠️ stale flag when untouched past the threshold. 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.
- 1mo ago Changed · +5 lines 8387c4ebf19c
- 1mo ago First seen · 31 lines · 44 tokens per session scan A 846584f7ab21
speckit-spec-stats-open is a skill published in the GitHub repository arrrrny/zuraffa (5 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 262 once invoked, about $0.0002 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 skills, from other repositories
he-plan
Plan a change before implementation, resolve material user decisions and prepare repository-grounded UX references. Use a compact plan for small changes; route large, unclear efforts or explicit Wayfinder requests to Wayfinder. Skip explanation-only requests and execution already covered by a ready, authorized plan.
he-build
Implement and verify a ready, authorized plan through focused fixes and integrated checks, ending with a ready-for-ship handoff. Use for implementation, bug fixes or resuming build work; skip planning-only, review-only and shipping-only requests.
he-ship
Deliver a verified build through a task branch and PR, check the intended remote result, and clean up the completed task safely. Use for PR creation, shipping, merging or release/deployment requests; skip planning, implementation and review-only work.
he-learn
Prevent verified repeated failures and preserve lasting decisions in terse ADRs. Use when failures recur, prevention needs strengthening, or accepted decisions and steering need durable capture; skip ordinary one-off fixes and routine task updates.
he
Apply Hard Eng's planning, project context, verification and gate-adaptation guidance when implementing or reviewing code in an installed project.
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.