A command that checks the health of a Spec Kit project, including its templates, agent setup, Python runner, constitution, and feature files. Spec Kit is a project structure for developing software from written specifications.

Use it to verify project setup, find missing templates or commands, and check that feature artifacts and supporting tools are configured.

It quickly reveals missing or empty files and incorrect configuration that could stop the specification workflow from running correctly.

How racecraft-lab/racecraft-plugins-public configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to racecraft-lab/racecraft-plugins-public. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/racecraft-lab/racecraft-plugins-public/main/.specify/extensions/speckit-utils/commands/doctor.md

Clone the repo

git clone --depth 1 https://github.com/racecraft-lab/racecraft-plugins-public

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/racecraft-lab/racecraft-plugins-public/doctor/github.svg)](https://agentmods.dev/commands/racecraft-lab/racecraft-plugins-public/doctor)

Your own site

<a href="https://agentmods.dev/commands/racecraft-lab/racecraft-plugins-public/doctor"><img src="https://agentmods.dev/badge/commands/racecraft-lab/racecraft-plugins-public/doctor/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/racecraft-lab/racecraft-plugins-public/doctor"><img src="https://agentmods.dev/badge/commands/racecraft-lab/racecraft-plugins-public/doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 867 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00018	$0.00867
Opus 5	$0.00009	$0.00434
Sonnet 5	$0.00004	$0.00173
Haiku 4.5	$0.00002	$0.00087

Measured 9d ago against content hash c9ba51cb05c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

doctor 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 9d 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.

.specify/extensions/speckit-utils/commands/doctor.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

User Input

$ARGUMENTS

Outline

Run a comprehensive health check on the spec-kit project, validating that all required components are present and correctly configured.

Step 1: Find the project root

Locate the .specify/ directory. If not found, error: "No spec-kit project found. Run specify init first."

Step 2: Check templates

Verify these template files exist in templates/ and are non-empty:

spec-template.md
plan-template.md
tasks-template.md
constitution-template.md
checklist-template.md

For each template:

File exists and non-empty: PASS
File exists but empty: WARN ("template is empty")
File missing: FAIL ("template not found")

Step 3: Check agent configuration

Read .specify/init-options.json to determine the configured AI agent.

If no init-options.json exists: WARN ("no AI agent configured - run specify init to set up")

If an agent is configured (e.g., "ai_assistant": "claude"):

Check that the agent's directory exists (e.g., .claude/)
Check that command files are registered (e.g., .claude/commands/speckit.*.md)
Count registered commands

Agent dir exists with commands: PASS
Agent dir missing: FAIL ("agent directory not found")
Agent dir exists but no commands: WARN ("no command files registered")

Step 4: Check the Python runner and helpers

Look for the current SpecKit Pro runner package in either location:

Source checkout, relative to the project root: speckit-pro/speckit_pro_runner/
Installed payload, relative to the resolved plugin root: speckit_pro_runner/

If a runner package is present, verify these files exist and are non-empty:

__main__.py
runtime.py
helpers/registry.py
gates/registry.py
speckit-pro-runner.manifest.json
speckit-pro-runner.sha256

Read the manifest with Python standard-library json and confirm it is a JSON object.

Runner package and all required files are valid: PASS
Runner package exists but a required file is missing, empty, or invalid: FAIL
Neither runner location exists: WARN ("SpecKit Pro Python runner not found - skipping plugin runtime layout checks")

Read the full file on GitHub · 112 lines

Changes

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.

9d ago First seen · 112 lines · 18 tokens per session scan A c9ba51cb05c7

Subscribe to this mod's changes

doctor is a command published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 867 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-31.

Claude Code Debugging claude-plugins mcp skills spec-driven-development

check

Drift detector. Diff SPEC.md against code. Read-only, zero writes.

JuliusBrussee/cavekit · 16 tokens

debug-pod

Debug a failing or unhealthy Kubernetes pod by analyzing events, logs, and configuration.

rohitg00/awesome-claude-code-toolkit · 0 tokens

map

Generate a dependency map showing how modules and files relate to each other in the codebase.

rohitg00/awesome-claude-code-toolkit · 0 tokens

code-locate

Given a behavior description, locate candidate code paths and line ranges in the active codebase that probably implement it. Output up to 10 candidates with HIGH/MEDIUM/LOW confidence, one-line rationale per candidate, and an explicit search trail; propose a SOURCEOFTRUTH.md update so the next workflow step (typically…

Mozurok/fhorja.dev · 209 tokens

optimizer

Performance optimization with systematic analysis and improvements.

smith-horn/skillsmith · 0 tokens

triage

Triage a bug report (PDF / markdown / text) — extract the issues, prioritize, then run the fix pipeline per issue.

Jewgah/claude-code-skills · 27 tokens

racecraft-plugins-public: Command for Claude Code