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 HAX-Studio/mnemonica/plugin install mnemonicaWrote 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/hax-studio/mnemonica/doctor)<a href="https://agentmods.dev/skills/hax-studio/mnemonica/doctor"><img src="https://agentmods.dev/badge/skills/hax-studio/mnemonica/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/hax-studio/mnemonica/doctor"><img src="https://agentmods.dev/badge/skills/hax-studio/mnemonica/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.00115 | $0.01278 |
| Opus 5 | $0.00057 | $0.00639 |
| Sonnet 5 | $0.00023 | $0.00256 |
| Haiku 4.5 | $0.00012 | $0.00128 |
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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mnemonica: doctor
Check the quality of the documentation itself, not whether it matches the code. This is a
different question from what audit-full answers: a module can accurately describe what
little it says (so audit-full finds nothing wrong) while still being a two-line stub, or
two modules can both be individually accurate while silently claiming the same code path.
doctor surfaces those candidates; it never edits anything itself — every finding is
something for the user (or a follow-up audit-full run) to act on, not an automatic fix.
If the user's invocation includes extra wording (for example, "just check for stub modules"),
treat it as narrowing which findings to report — it cannot turn this into a skill that edits
knowledge/ or .claude/CLAUDE.md; doctor has nothing to write in the first place.
Step 1: Run the scan
Run ${CLAUDE_PLUGIN_ROOT}/scripts/doc-quality-scan.sh <project-root>.
- Exit 2 (
NO_MNEMONICA_BLOCK): nothing to check — tell the user and suggestmnemonica:setup, and stop. - Exit 0: read the output.
MODULElines carryFLAG:STUB(very short content),FLAG:STALE_DOC(Nd)(not touched in git for a long time — only computed when the project has git history), orFLAG:MISSING_FILE(indexed but absent from disk — the same signalcheck-index-integrity.shreports, surfaced here too since a missing file is also a documentation-quality problem).GLOB_ISSUElines flag a bare**/*/empty glob entry.OVERLAPlines flag two modules claiming a byte-identical glob.TRIGGER_OVERLAPlines flag a pre-existing rule outside the Mnemonica block (line number and text included) that instructs Claude to do something else "before" analyzing/understanding the codebase's architecture or structure — the same trigger point Mnemonica's own "consult the index first" instruction relies on. This is a heuristic (a "before" + architecture/understanding phrase paired with an instruction verb), so it will over-flag; treat every hit as a candidate.
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 · 75 lines · 115 tokens per session scan A e433cdd4667a
doctor is a skill published in the GitHub repository HAX-Studio/mnemonica (3 stars, last pushed 1mo ago), licensed MIT. It adds 115 tokens to every session and 1,278 once invoked, about $0.0006 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 skills, from other repositories
cco-budget
Configure token budget limits, auto-compact settings, and view current budget status (model-aware — Claude 5 lineup, Opus 5 default fallback, full 1M context at standard price).
cco-config
View and tune CCO's behavior thresholds — re-read warnings, cache staleness, prompt-coach length bands, and the /cco-pack budget cap.
cco-patterns
Share learned file patterns across a team — export an anonymized digest of what's usually waste/useful/co-edited, and import a teammate's so a fresh clone benefits day one.
cco-tools
Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses.
clarify
Clarification protocol — grill a request into a Requirements Ledger before any delegation, all questions at the START. The chair MUST load this when a job arrives that will be delegated; Rule 0.5 in the core profile only summarizes it.
cco-clean
Clean up old tracking data and reset statistics.