doctor

doctor is a skill for Claude Code from WinterDDo/claude-code-skill-autopilot. It costs 61 tokens per session (653 once invoked), scanned A, original, MIT.

A diagnostic skill for checking whether Skill Autopilot hooks and settings are working. Hooks are automatic actions that run when certain events occur.

In plain words
What is it for?
Use it after installation or when suggestions stop appearing to check the current session, the hook canary, and the indexed skills.
Why use it?
Autopilot can appear inactive when its hooks are not loaded, not firing, or not surfacing skills. This separates those possible problems and reports what is actually working.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: reads .claude/ paths; mentions Claude Code.

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 skill-autopilot plugin — 6 skills, 4 hooks shipped together

Good fit Use it after installation or when suggestions stop appearing to check the current session, the hook canary, and the indexed skills.

Compare 6 skills from other repositories ↓
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 WinterDDo/claude-code-skill-autopilot
Claude Code
/plugin install skill-autopilot

Made for: Claude Code.

Or install skill-autopilot, the plugin that ships this one along with the rest of its 6 skills, 4 hooks.

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 doctor

README.md
[![agentmods](https://agentmods.dev/badge/skills/winterddo/claude-code-skill-autopilot/doctor/github.svg)](https://agentmods.dev/skills/winterddo/claude-code-skill-autopilot/doctor)
Your own site
<a href="https://agentmods.dev/skills/winterddo/claude-code-skill-autopilot/doctor"><img src="https://agentmods.dev/badge/skills/winterddo/claude-code-skill-autopilot/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.

agentmods 80×15 button for doctor

Your own site · 80×15
<a href="https://agentmods.dev/skills/winterddo/claude-code-skill-autopilot/doctor"><img src="https://agentmods.dev/badge/skills/winterddo/claude-code-skill-autopilot/doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 653 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.00061 $0.00653
Opus 5.5 $0.00024 $0.00261
Sonnet 5.5 $0.00012 $0.00131
Haiku 4.5 $0.00006 $0.00065

Measured 1mo ago against content hash 2af5eab88275, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

plugins/skill-autopilot/skills/doctor/SKILL.md · 53 lines

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.

Autopilot health check

Two independent checks. Report both, then a one-line verdict.

Check 1 — self report (only the model can confirm this)

State plainly, first: did the CURRENT prompt's context contain a block starting with [AUTOPILOT]? Yes or no. If yes, injection reaches the model — the core product works.

Check 2 — the canary

Run:

sh "${CLAUDE_PLUGIN_ROOT}/hooks/run.sh" doctor-noop 2>/dev/null; python3 "${CLAUDE_PLUGIN_ROOT}/scripts/doctor.py" "$HOME/.claude/command-autopilot" "<current session id if known>"

Read the output. Key line is router canary: if it shows THIS session, the hook fired end-to-end. If it says NEVER FIRED, tell the user to restart Claude Code (hooks load at startup) and run this skill again.

Check 3 — skills surfacing (read-only; the Skills Autopilot layer)

Report what the skill layer sees and has done. All read-only, no writes:

python3 - <<'EOF'
import json, os
d = os.path.expanduser("~/.claude/command-autopilot")
try:
    idx = json.load(open(d + "/skills-index.json")); b = idx.get("budget", {})
    print("skills indexed:", len(idx.get("skills", [])),
          "| parked (native can't auto-fire these):", b.get("parked_count"),
          "| over native budget:", b.get("over_budget"))
except Exception:
    print("no skills index yet — restart Claude Code so SessionStart builds it")
try:
    s = json.load(open(d + "/state.json")); w = s.get("counters", {}).get("wake", {})
    f = lambda k: sum(v.get(k, 0) for v in w.values())
    print("wake popups — shown:", f("shown"), "accepted:", f("accepted"), "declined:", f("declined"))
except Exception:
    pass
EOF

Report in one line: N skills installed, M parked (invisible to native — the ones the autopilot uniquely surfaces), and the wake shown/accepted tally. If shown is still 0 after real use, surfacing isn't firing yet — say so honestly; the real ledger is the judge, not assumptions.

Verdict

  • Both pass → "Autopilot is healthy." Show the config line so the user sees their current mode.
  • Check 1 fails but files look fine → restart needed, or another hook is crowding the context; suggest restart first.
  • Python missing in check 2 → explain stateless mode honestly: core rules still work, learning and evidence are paused until Python 3.8+ is installed.

Read the full file on GitHub · 53 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.

  1. 1mo ago First seen · 53 lines · 61 tokens per session scan A 2af5eab88275

Subscribe to this mod's changes

doctor is a skill published in the GitHub repository WinterDDo/claude-code-skill-autopilot (6 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 653 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

skill-debug

Debug a reproducible symptom with a bounded feedback loop and original-scenario verification.

nyldn/claude-octopus · 18 tokens

linux

Linux administration and networking diagnostics — DNS, load balancing, VPCs, kernel tuning, and connectivity troubleshooting.

nitinjain999/platform-skills · 24 tokens

chaos

Design, run, and debug Chaos Engineering experiments on Kubernetes using Litmus Chaos v3 and Chaos Mesh v2. Covers fault injection (pod-delete, network-loss, CPU stress, node-drain), steady-state hypothesis probes, GameDay runbooks, scheduled experiments, DORA feedback loop, and RBAC setup. Use when asked to "inject a…

nitinjain999/platform-skills · 97 tokens

debug

Structured platform troubleshooting — classifies the problem layer, collects evidence, forms a root-cause hypothesis, and proposes a fix with validation and rollback steps.

nitinjain999/platform-skills · 32 tokens

rubber-ducky

Use when you've planned a non-trivial change and are about to implement it, finished a complex or multi-file piece of work, just wrote tests, or are stuck on repeated failures or unexpected results — and any time the user says "rubber duck this", "rubber ducky", "get a second opinion", "sanity-check my plan", "poke…

harnessprotocol/harness-kit · 189 tokens

ia-verification-before-completion

Enforces fresh verification evidence before any completion claim. Use when about to claim "tests pass", "bug fixed", "done", "ready to merge", handing off work, or before editing when a request has ambiguous scope.

iliaal/whetstone · 52 tokens