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.
npx agentmods add commands/rami-code-review/claude-code-marketplace/doctorgit clone --depth 1 https://github.com/rami-code-review/claude-code-marketplaceWrote 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/rami-code-review/claude-code-marketplace/doctor)<a href="https://agentmods.dev/commands/rami-code-review/claude-code-marketplace/doctor"><img src="https://agentmods.dev/badge/commands/rami-code-review/claude-code-marketplace/doctor.svg" alt="Measured on agentmods" 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.00124 |
| Opus 5 | $0.00010 | $0.00062 |
| Sonnet 5 | $0.00004 | $0.00025 |
| Haiku 4.5 | $0.00002 | $0.00012 |
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 5d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 5d ago First seen · 10 lines · 20 tokens per session scan A 728adf66f0a3
doctor is a command published in the GitHub repository rami-code-review/claude-code-marketplace (0 stars, last pushed 4d ago), with no licence file. It adds 20 tokens to every session and 124 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
logic-fix-all
Autonomous audit-and-fix — after consent, scan the target, fix every logic issue found (all severities), verify each fix, and report anything unresolved.
logic-health
Sweep a whole codebase or directory for logic correctness — use before a release or to identify risk hotspots.
logic-locate
Locate the root cause of a confirmed failure — use when you have a stack trace, failing test, or wrong output.
logic-review
Review code for logic bugs — use when you suspect something is wrong but have no failing test yet.
logic-explain
Trace execution step by step — use when code behavior is surprising or confusing.
sm-refit
Run slop-mop's one-time onboarding remediation rail for this repository.