doctor

A preflight report for the DeepInit project-analysis tool. It checks available developer tools, project scope, configuration, enabled issue categories, and estimated analysis cost without using language-model tokens or changing files.

In plain words
What is it for?
Use it to inspect detected tools, database and Git availability, resolved settings, configuration validity, enabled checks, and whether freshness hooks can be installed.
Why use it?
It shows whether the planned analysis has the tools and valid settings it needs before you run it. It also exposes missing tools and configuration problems early.

Command

Part of the deep-init plugin — 1 skill, 9 commands, 2 hooks shipped together

Install

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.

agentmods
npx agentmods add commands/deepfusionlabs/deep-init/doctor
Clone the repo
git clone --depth 1 https://github.com/deepfusionlabs/deep-init

Or install deep-init, the plugin that ships this one along with the rest of its 1 skill, 9 commands, 2 hooks.

Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 531 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00039 $0.00531
Opus 5 $0.00019 $0.00266
Sonnet 5 $0.00008 $0.00106
Haiku 4.5 $0.00004 $0.00053

Measured 2d ago against content hash 3d2079d576c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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/doctor.md · 17 lines

What it actually says

Run the deep-init skill's preflight report (--doctor) — 0 tokens, no LLM, no analysis, no writes. Load skills/deep-init/SKILL.md and report:

  • Version & freshness — read .claude-plugin/plugin.json for the on-disk version; for the version actually loaded in this session (and a stale-reload check) run /deep-init:version. Claude Code loads plugin markdown once per session, so activation is host-dependent: in a plain terminal a new session (or /reload-plugins) picks it up; inside the VS Code/JetBrains extension you must restart the IDE itselfDeveloper: Reload Window does not reload the plugin host.
  • Tools detected — scc, Graphify, ctags, a DB client, gitleaks/trufflehog (and what each falls back to if missing — nothing aborts a run).
  • Scope — the component registry, whether a DB / git history is present and in scope.
  • Resolved settings — the effective config (built-in max-quality defaults ← .ai/deepinit.config ← any flags), and whether .ai/deepinit.config is valid against skills/deep-init/assets/deepinit.config.schema.json (report unknown/invalid keys — warn, never fatal, R8).
  • Enabled issue families and the estimated cost (base + issue-pass terms).
  • Freshness nudge — would it fire now? Run deepinit_status.py --explain (0 tokens, no LLM) and show its verdict: docs stale or fresh, whether the SessionStart nudge is enabled or disabled (and by which switch), the cadence/window, the last-nudge state, and any active [Not now] decline-snooze. This answers "why am I not seeing the staleness nudge?" without guesswork.

Then OFFER (do not auto-run) to install the freshness triggers via setup-hooks — the deepinit_status.py keystone + the post-commit + SessionStart hooks (references/triggers.md) — and point to /deep-init:customize → Freshness to change the cadence / window or turn the nudge off. Make no changes.

$ARGUMENTS

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. 2d ago First seen · 17 lines · 39 tokens per session scan A 3d2079d576c7

Subscribe to this mod's changes

doctor is a command published in the GitHub repository deepfusionlabs/deep-init (6 stars, last pushed 14d ago), licensed MIT. It adds 39 tokens to every session and 531 once invoked, about $0.0002 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.