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/Paddock --skill speckit-doctor-checkgit clone --depth 1 https://github.com/racecraft-lab/PaddockWrote 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/paddock/speckit-doctor-check)<a href="https://agentmods.dev/skills/racecraft-lab/paddock/speckit-doctor-check"><img src="https://agentmods.dev/badge/skills/racecraft-lab/paddock/speckit-doctor-check/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/paddock/speckit-doctor-check"><img src="https://agentmods.dev/badge/skills/racecraft-lab/paddock/speckit-doctor-check.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.00029 | $0.00480 |
| Opus 5 | $0.00015 | $0.00240 |
| Sonnet 5 | $0.00006 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
speckit-doctor-check 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- speckit-doctor — 94% identical, 2 lines differ
What it actually says
Project Health Check
Run a diagnostic scan of the current Spec Kit project to identify setup issues, missing artifacts, and configuration problems.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Outline
-
Run diagnostic script: Execute
.specify/extensions/doctor/scripts/bash/doctor.shfrom the project root and review the output. -
Analyze results: The script checks 6 areas:
- Project structure —
.specify/,specs/,.specify/scripts/,.specify/templates/,.specify/memory/,.specify/memory/constitution.md - AI agent configuration — detects which agent folder is present, verifies commands exist
- Feature specifications — lists features in
specs/, checks for spec.md/plan.md/tasks.md - Scripts health — verifies all bash and PowerShell scripts are present and executable
- Extensions health — validates extensions.yml and extension registry
- Git status — checks if inside a git repo, shows current branch
- Project structure —
-
Report findings: Present the diagnostic results to the user:
- Errors — things that are broken and need fixing
- Warnings — things that could cause problems
- Notes — informational items about the project state
-
Suggest fixes: For each error or warning found, suggest the specific command or action needed to resolve it. Common fixes include:
- Missing directories →
specify init --here - Missing constitution → copy from
.specify/templates/constitution-template.md - Missing feature artifacts → run
/speckit.planor/speckit.tasks - Non-executable scripts →
chmod +x .specify/scripts/bash/*.sh - Empty agent commands →
specify init --here --ai <agent>
- Missing directories →
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.
- 12d ago First seen · 45 lines · 29 tokens per session scan A ccda74cabc39
speckit-doctor-check is a skill published in the GitHub repository racecraft-lab/Paddock (12 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 480 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
nextjs-app-router-dev
A skill for developing and troubleshooting Next.js applications that use the App Router, including Edge middleware, SQLite, and session-based authentication.
rust-check
Run cargo check on the current Rust project to find compile errors.
debug
Reproduce, minimize, localize, identify root cause, and distinguish diagnosis from an authorized fix. Prefer root-cause over symptom patches.
langsmith-tracing
LangSmith tracing and debugging setup for LLM applications. Configure observability, capture traces, and enable debugging for LangChain/LangGraph agents.
systematic-debugging
4-phase root cause analysis: observe, hypothesize, verify, fix. Enforces investigation before any code changes. Emergency stop after 2 failed fixes. Prevents shotgun debugging and fix cascades.