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-coachgit 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-coach)<a href="https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/speckit-coach"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-coach/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-coach"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-coach.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.00080 | $0.01403 |
| Opus 5 | $0.00040 | $0.00701 |
| Sonnet 5 | $0.00016 | $0.00281 |
| Haiku 4.5 | $0.00008 | $0.00140 |
Grade A, and why
speckit-coach 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 yesterday.
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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecKit Coach
Coach the user through the official SpecKit CLI and complementary SpecKit Pro workflows. This skill provides guidance and bounded project repair; it does not run an autonomous workflow itself. In Codex, use $skill-name syntax for plugin skills rather than legacy custom slash-command syntax.
Start with the project that exists
- Use
speckit-pro/skills/speckit-autopilot/references/capability-discovery.mdfor capability selection andspeckit-pro/skills/speckit-autopilot/references/grounding.mdfor external-fact grounding. - Discover the session's available tools and skills before recommending an external action. Ground external claims in an observed result; say when the available evidence is insufficient.
- Inspect
.specify/presets/*/preset.ymland.specify/extensions/*/extension.ymlwhen present. Read the installed configuration before advising, so the advice reflects the project's actual constraints. - Treat mutable actions as user-controlled. Explain the intended change and request confirmation before installing, removing, enabling, disabling, or configuring extensions.
Route the request
Use the smallest relevant reference; do not load the whole library.
| User goal | Read or do |
|---|---|
| Learn SDD, start a project, recover from a failed phase, or assess artifacts | Getting started and SDD methodology as needed. |
| Use an installed official Spec Kit command | Command guide for inputs, artifacts, mistakes, and recovery. Inspect the active installed command definition for version-specific mechanics. For gate questions, read the live autopilot contract as a reference only; do not execute or invoke it. |
| Choose or author checklists | Checklist domains. Read the feature's spec.md and plan.md, rank the relevant risks, and offer enriched prompts for two to four domains. |
| Decide whether a behavior needs formal verification, choose a checker, or learn a first model | Selective formal methods. Assess risk and simpler checks first; record explicit selection and adapt coaching to experience. |
| Design a constitution | Constitution guide. |
Create or repair .specify/quality-gates.json, pick gate thresholds, or record a permanent gate skip |
Quality gates guide. Measure the existing code before proposing a ceiling; write the file only after the operator confirms. |
| Design a multi-spec roadmap or split a feature | Technical-roadmap template and slicing heuristics. Derive independently executable vertical slices with observable outcomes and explicit real dependencies; review the graph before writing. |
| Create a PRD and roadmap from an unformed idea | Route to $speckit-prd; use its PRD and roadmap templates. |
| Track one spec through phases or understand scaffold-created workflow files | Workflow template. For scaffold creation, population, inputs, or output locations, also read the live scaffold skill as a reference only; do not execute or invoke it. Keep artifacts, gates, and decisions current. |
| Explain the roadmap home note | Roadmap-MOC guide. The curated zone is author-owned; the generated index is regenerated, not hand-edited. |
| Explain or configure presets, extensions, hooks, catalogs, or upgrade recovery | Presets and extensions guide. Discover and inspect first; confirm before any mutation. |
| Explain autonomous execution, consensus, remediation, review loops, or configuration | Read the live autopilot skill as a reference only; explain its current contract without executing or invoking it. |
| Scope a raw brief interactively | Route to $grill-me; do not conduct its interview here. |
| Scaffold a roadmap item, inspect status, resolve a review, or repair Codex agents | Route respectively to $speckit-scaffold-spec, $speckit-status, $speckit-resolve-pr, or the SpecKit Pro install skill. |
| Archive merged-spec records or clean up archived specs | Route to $speckit-archive-cleanup; do not copy or execute its cleanup workflow here. |
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.
- yesterday Changed · +1 lines 0e734d6b4815
- 2d ago Changed · -323 lines · -133 tokens per session 97616313051c
- 8d ago First seen · 375 lines · 213 tokens per session scan A e7ad440e4bb4
speckit-coach is a skill published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 1,403 once invoked, about $0.0004 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
google-agents-cli-onboarding
Onboarding entrypoint for agents-cli in Agent Platform. It should be used when the user wants to "create a new agent", "develop an agent", "build an agent using ADK", "run the agent locally", "debug agent code", "test an agent", "evaluate an agent", "deploy an agent", "publish an agent", "monitor an agent", or needs…
practice-cognition
A method for testing ideas in practice, learning from the results, and improving the next attempt through repeated cycles.
build-executor
Govern implementation from an approved execution contract. Invoke when execution-contract.md is approved and the user wants disciplined build work, TDD execution, or guarded batch-by-batch implementation.
36-anthropic-agents-kit-development
Create your Claude Agent SDK skill in one prompt, then learn to improve it throughout the chapter.
need-explorer
Clarify intent, scope, constraints, and success criteria before artifact creation. Invoke when the request is fuzzy, the user is comparing options, or the workflow needs a stable change definition before writing artifacts.
academy-guide
Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude…