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.
npx skills add racecraft-lab/racecraft-plugins-public --skill speckit-statusgit clone --depth 1 https://github.com/racecraft-lab/racecraft-plugins-publicWrote 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/racecraft-lab/racecraft-plugins-public/speckit-status)<a href="https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/speckit-status"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-status/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/racecraft-lab/racecraft-plugins-public/speckit-status"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00119 | $0.02360 |
| Opus 5 | $0.00060 | $0.01180 |
| Sonnet 5 | $0.00024 | $0.00472 |
| Haiku 4.5 | $0.00012 | $0.00236 |
Grade A, and why
speckit-status 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecKit Status
Installed Runtime Contract
Installed Claude and Codex surfaces resolve Python 3.11 or newer, invoke
[resolved_python, "-m", "speckit_pro_runner"], send one JSON request on
stdin, read one JSON response from stdout, and surface stderr diagnostics.
Do not add a shell fallback, jq parsing path, Git Bash, WSL, or
PowerShell-specific command-language requirement for installed workflows.
Scope
Use this skill when the user wants to know what is in progress, what is blocked, what has already shipped, or which spec should be started next. This is the read-only project dashboard for SpecKit workflows. It should summarize both the high-level roadmap and the phase-level progress inside workflow files.
If the user wants help understanding SDD methodology, checklist domains, or how
to fix a failing gate, redirect to $speckit-coach. If the user wants to
execute a populated workflow, redirect to $speckit-autopilot. This skill is
for status, synthesis, and next-step recommendation.
Input
Accept either:
- no argument, meaning “show the overall roadmap”
all, which is the same as the overall roadmap view- a specific
SPEC-IDsuch asSPEC-013
When no argument is provided, prefer the full dashboard. When a SPEC-ID is
provided, show the targeted detail view for that spec first.
What to Read
Search the repository and any attached git worktrees for both of the following before answering:
- technical roadmap files, typically matching
*technical-roadmap*or*roadmap* - workflow files, typically matching
*-workflow.md - archive extension state files when present:
.specify/extensions.yml,.specify/extensions/.registry,.specify/extensions/archive/extension.yml, and.specify/extensions/archive/RACECRAFT-PIN.md
Do not assume the user keeps everything under one directory. Search the current
checkout first, then inspect git worktree list --porcelain so workflows in
attached worktrees are included even when setup used a nonstandard worktree
root. Narrow to the files that actually describe the SpecKit project. If a file
looks unrelated, ignore it rather than polluting the dashboard.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +4 lines · +74 tokens per session 2b25049e9688
- 6d ago First seen · 253 lines · 45 tokens per session scan A c591849ffb16
speckit-status is a skill published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed today), licensed MIT. It adds 119 tokens to every session and 2,360 once invoked, about $0.0006 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-04.
Other skills, from other repositories
codex-issue-coordinator
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
plan
Turns an approved design or decided brief into ordered tasks for separate agent runs. Use for implementation tasks, tracker tickets, or useful milestones. Do not use for one coding task or its short execution outline.
to-issues
Break a plan or PRD into vertical-slice issues on the project issue tracker.
to-prd
Synthesize the current conversation into a PRD and publish to the issue tracker. No interview — use what you already know.
spec-to-done
Drive a reviewed spec to evidence-backed, integrated closure — grill the spec at intake until it is fully understood, decompose it into owned work items, build each against targeted criteria, gate every merge per item, maintain a criterion-to-evidence ledger, and close only when an integrated done gate passes. Use…
triage
Move issues and external PRs through triage roles — categorise, verify, grill if needed, write agent-ready briefs.