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 skills add bobmatnyc/claude-mpm --skill mpm-doctorgit clone --depth 1 https://github.com/bobmatnyc/claude-mpmWrote 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/skills/bobmatnyc/claude-mpm/mpm-doctor)<a href="https://agentmods.dev/skills/bobmatnyc/claude-mpm/mpm-doctor"><img src="https://agentmods.dev/badge/skills/bobmatnyc/claude-mpm/mpm-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/skills/bobmatnyc/claude-mpm/mpm-doctor"><img src="https://agentmods.dev/badge/skills/bobmatnyc/claude-mpm/mpm-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.00013 | $0.00318 |
| Opus 5 | $0.00006 | $0.00159 |
| Sonnet 5 | $0.00003 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
mpm-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 12d 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 12d ago First seen · 54 lines · 13 tokens per session scan A 13ee8190e5ea
mpm-doctor is a skill published in the GitHub repository bobmatnyc/claude-mpm (151 stars, last pushed 12d ago), with no licence file. It adds 13 tokens to every session and 318 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-30.
Other skills, from other repositories
System Healthcheck
Run a lightweight, non-destructive system healthcheck — disk usage, memory, CPU load, process count, hostname — and store a structured snapshot in session memory. Use when the user says "run a healthcheck", "check system health", "how's the server doing", "is everything ok", or asks for a status/diagnostics snapshot…
debugging
Systematically diagnose and fix bugs using structured debugging techniques. Use when investigating errors, unexpected behavior, failing tests, or production issues.
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
seedance-troubleshoot
This skill should be used when a Seedance 2.0 output is blurry, jittery, off-prompt, morphing, blocked, visually generic, unstable, desynced, inconsistent, or otherwise fails and needs root-cause diagnosis.
atmos-introspection
Introspection & Querying: describe/list commands, config filtering, workspace introspection, dependency graphs, YQ integration, --help= scoped CLI help.
atmos-schemas
JSON Schema for Atmos: stack-manifest and atmos.yaml config schemas, IDE auto-completion, validate stacks/schema/config, SchemaStore integration.