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 sigistry/marketplace/plugin install recordsWrote 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/sigistry/marketplace/doctor)<a href="https://agentmods.dev/commands/sigistry/marketplace/doctor"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/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/sigistry/marketplace/doctor"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/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.00020 | $0.00266 |
| Opus 5 | $0.00010 | $0.00133 |
| Sonnet 5 | $0.00004 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00027 |
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 6d 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.
What it actually says
Records FHIR Validation Doctor
Use the fhir-project-doctor skill for this diagnostic task.
Target: $ARGUMENTS or the current working directory.
Run the deterministic detector, runtime planner, and package doctor when available:
node "${CLAUDE_PLUGIN_ROOT}/skills/fhir-validation/scripts/detect-fhir-project.mjs" "$ARGUMENTS"
node "${CLAUDE_PLUGIN_ROOT}/skills/fhir-validation/scripts/plan-runtime.mjs" "$ARGUMENTS"
node "${CLAUDE_PLUGIN_ROOT}/skills/fhir-validation/scripts/doctor-packages.mjs" "$ARGUMENTS"
If no argument was provided, use .. Summarize:
- Project type and source/generated directories.
- Workflow files and existing CI validation hooks.
- Available Records, SUSHI, Java validator, Firely, or HAPI runtimes.
- Recommended validation order.
- Privacy warnings and any consent gates before network/server/API use.
- Package-cache findings, missing dependencies, mixed FHIR versions, and setup-vs-resource defects.
Do not edit files unless the user explicitly asks for fixes.
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.
- 6d ago First seen · 30 lines · 20 tokens per session scan A 2b2085325a16
doctor is a command published in the GitHub repository sigistry/marketplace (3 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 266 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-09-03.
Other commands, from other repositories
octo-loop
Your first output line MUST be: 🐙 Octopus Loop Mode.
octo-debug
Debug a symptom through reproducible, bounded evidence.
five-whys
Use the "Five Whys" root cause analysis technique to deeply understand problems.
debug
Structured debugging with parallel investigation agents.
bugfix
TDD-driven bugfix workflow: tester writes failing test (RED) → developer fixes (GREEN) → developer refactors (REFACTOR) → reviewer validates. Accepts issue number, description, or both. Auto-creates PR unless --no-pr flag is passed.
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.