agentmods.dev

spec-doctor

spec-doctor is a command for Claude Code from Connorrmcd6/vibe-spec. It costs 51 tokens per session (606 once invoked), scanned A, original, MIT.

A read-only command that checks whether common development tools are installed and reports their versions. It checks tools such as Git, Node, pnpm, Docker, and uv.

In plain words
What is it for?
Use it before working with the Vibe-Spec development setup to check your operating system, installed tools, Docker status, and next troubleshooting step.
Why use it?
It quickly shows which prerequisites are missing or not working without installing or changing anything on your computer.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the vibe-spec plugin — 1 skill, 9 commands shipped together

not rated 9repo 2mo ago A scan 51 tokens original MIT

Good fit Use it before working with the Vibe-Spec development setup to check your operating system, installed tools, Docker status, and next troubleshooting step.

Compare 6 commands from other repositories ↓
View source ↗ Connorrmcd6/vibe-spec vibe-spec.gradientdev.xyz
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add Connorrmcd6/vibe-spec
Claude Code
/plugin install vibe-spec

Made for: Claude Code.

Or install vibe-spec, the plugin that ships this one along with the rest of its 1 skill, 9 commands.

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.

agentmods badge for spec-doctor

README.md
[![agentmods](https://agentmods.dev/badge/commands/connorrmcd6/vibe-spec/spec-doctor.svg)](https://agentmods.dev/commands/connorrmcd6/vibe-spec/spec-doctor)
Your own site
<a href="https://agentmods.dev/commands/connorrmcd6/vibe-spec/spec-doctor"><img src="https://agentmods.dev/badge/commands/connorrmcd6/vibe-spec/spec-doctor.svg" alt="Measured on agentmods" height="20"></a>
Per session 51 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 606 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.00606
Opus 5 $0.00026 $0.00303
Sonnet 5 $0.00010 $0.00121
Haiku 4.5 $0.00005 $0.00061

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

Security

Grade A, and why

spec-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 8d 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.

commands/spec-doctor.md · 44 lines

What it actually says

You are running /spec-doctor: a read-only health check of the user's development environment. Consult the vibe-spec skill (${CLAUDE_PLUGIN_ROOT}/skills/vibe-spec/reference/18-prerequisites.md) for the canonical tool list and detection commands.

You must not install, modify, or configure anything. This command only reports. If something is missing, point the user at /spec-setup; if a tool is present but misbehaving, point them at /spec-troubleshoot.

What to do

  1. Detect the OS once (uname -s on macOS/Linux; note if on Windows).

  2. From reference/18-prerequisites.md, run each tool's detection command with read-only Bash, capturing the version or the "not found" result:

    • git --version
    • node --version
    • pnpm --version
    • docker --version, then docker info (exit 0 = daemon running) and docker compose version
    • uv --version
    • gh --version (optional) Run independent checks together. Treat a non-zero exit or "command not found" as missing — do not error out; record it and continue.

  3. Print a compact status table with one row per tool:

    Tool Status Version Needed for

    Use ✓ for present, ✗ for missing. For Docker, surface the daemon state explicitly (e.g. "✓ installed, daemon not running"). Fill "Needed for" from the reference (e.g. Git → always; Node/pnpm → any web app; Docker → local Postgres; uv → dbt).

  4. Summarize in one or two lines: what's ready, what's missing, and which missing tools actually matter (note that Docker/uv are only needed for some project types).

  5. End by telling the user:

    • Run /spec-setup to install missing tools (guided, only what the project needs).
    • Run /spec-troubleshoot if a tool is installed but failing.

Keep the output scannable. Do not propose or run install commands here.

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.

  1. 8d ago First seen · 44 lines · 51 tokens per session scan A 424cb2c1dfa6

Subscribe to this mod's changes

spec-doctor is a command published in the GitHub repository Connorrmcd6/vibe-spec (9 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 606 once invoked, about $0.0003 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 CodeDebuggingai-assisted-developmentnextjspostgresqlprismaspec-driven
Related

Other commands, from other repositories

magic-wand

When /magic-wand [issue description] is invoked, immediately execute the following steps to perform a comprehensive, expert-level analysis and fix when standard debugging approaches have failed.

KaelSensei/MagicAIBuilder · 0 tokens

clean-code

When /clean-code [target] is invoked, immediately execute the following steps to remove redundant code, unused variables, dead code, debug statements, and other technical debt.

KaelSensei/MagicAIBuilder · 0 tokens

fix

When /fix is invoked, immediately execute the following steps.

KaelSensei/MagicAIBuilder · 0 tokens

cleanup-repo

When /cleanup-repo is invoked, immediately execute the following steps to analyze, organize, and clean up the repository structure when files are scattered and disorganized.

KaelSensei/MagicAIBuilder · 0 tokens

brainstorm

When /brainstorm [topic] is invoked, immediately execute the following steps to collaboratively brainstorm, enhance, and plan new features for the app through an iterative product management workflow.

KaelSensei/MagicAIBuilder · 0 tokens

devops

When /devops is invoked, immediately execute the following steps to create, configure, or manage DevOps infrastructure, CI/CD pipelines, and deployment configurations.

KaelSensei/MagicAIBuilder · 0 tokens