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.
/plugin marketplace add odere-pro/claude-wiki-pages-plugin/plugin install claude-wiki-pagesWrote 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/commands/odere-pro/claude-wiki-pages-plugin/doctor)<a href="https://agentmods.dev/commands/odere-pro/claude-wiki-pages-plugin/doctor"><img src="https://agentmods.dev/badge/commands/odere-pro/claude-wiki-pages-plugin/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.
<a href="https://agentmods.dev/commands/odere-pro/claude-wiki-pages-plugin/doctor"><img src="https://agentmods.dev/badge/commands/odere-pro/claude-wiki-pages-plugin/doctor.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.00555 |
| Opus 5 | $0.00015 | $0.00278 |
| Sonnet 5 | $0.00006 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00056 |
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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/claude-wiki-pages:doctor
The standard way to diagnose the plugin's own state. Prefer the engine doctor (ten checks D01–D10, agentline-style); fall back to the bash health script when Bun is unavailable.
Action
Run the engine doctor:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/engine.sh" doctor --json
It returns { results: [{ id, title, status, message, hint }], worst } where
status is pass | warn | fail | fixed | skip. To auto-repair the fixable
subset (D04 hook perms, D05 git init, D08 settings migration), add --fix. To
make warnings/failures gate CI, add --strict (exit 3 on any warn/fail).
| ID | Checks | --fix |
|---|---|---|
| D01 | Vault path resolves and exists | — |
| D02 | schema_version present and supported |
— |
| D03 | raw/ readable, wiki/ writable |
— |
| D04 | Every hooks.json script exists and is +x |
✓ chmod +x |
| D05 | Vault is a git repo (self-heal is reversible) | ✓ git init |
| D06 | Bun engine present | — |
| D07 | User config present / valid | — |
| D08 | Legacy settings path migrated | ✓ copy old → new |
| D09 | verify reports no errors |
hint: heal |
| D10 | Glossary gate (run in the plugin repo) | — |
If Bun is absent, engine.sh warns and exits 0 — then run the bash fallback,
which reports a coarser health status with exit codes 0–5:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/doctor.sh"
Surface the output and tell the user exactly which check to fix.
Companion command
/claude-wiki-pages:wiki— run the LLM Wiki itself once doctor reports healthy.
Specification anchor
Contracts: docs/architecture.md (diagnostics), SECURITY.md (security model — doctor is read-only by contract).
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 · 54 lines · 29 tokens per session scan A dfd69fec7f23
doctor is a command published in the GitHub repository odere-pro/claude-wiki-pages-plugin (1 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 555 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.
Other commands, from other repositories
techdebt
Find and report technical debt in the codebase.
crystallize
Promote extracted incident knowledge into global patterns and agent improvements.
audit
Audit an existing codebase. Detects stack, finds gaps, creates tasks, generates PROJECT.md.
fec-debug
Front-end problem diagnosis and repair: covering build failures, runtime errors, UI exceptions, and interface problems, using a unified diagnostic framework to classify problems by type.
fec-tdd
Use front-end TDD workflow to implement functions, fix bugs, or refactor logic: first write failing tests, then implement minimal code, and then refactor.
dead-code-scan
Scan for dead code, unused imports, duplicates, and zombie code across the project.