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 skills/yuno15-bb/c-brain/doctornpx skills add Yuno15-bb/c-brain --skill doctorgit clone --depth 1 https://github.com/Yuno15-bb/c-brainWrote 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/yuno15-bb/c-brain/doctor)<a href="https://agentmods.dev/skills/yuno15-bb/c-brain/doctor"><img src="https://agentmods.dev/badge/skills/yuno15-bb/c-brain/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.00059 | $0.00292 |
| Opus 5 | $0.00030 | $0.00146 |
| Sonnet 5 | $0.00012 | $0.00058 |
| Haiku 4.5 | $0.00006 | $0.00029 |
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
Check the trunk and the wiring
Two commands, and they answer different questions. Run both.
brain selftest # is the ENGINE wired correctly? (hooks, links, permissions)
brain doctor # is the TRUNK coherent? (dead [[links]], orphans, index gaps)
Reading the result
- selftest red → the installation is the problem. Re-run
install.sh; it is idempotent and repairs its own wiring. - doctor red → the notes are the problem. Dead
[[links]]and notes missing fromMEMORY.mdare the two that actually cost recall. - Both green but recall returns nothing → the query, not the machinery. Try narrower terms; the ranking is lexical, so it matches words, not meaning.
What not to conclude
A silent hook is not a healthy hook. If notes are not being saved and both commands are green, check that the hooks are registered at all — a hook whose path no longer resolves does not fail loudly, it simply stops recording.
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 · 28 lines · 59 tokens per session scan A c28cc5d8c632
doctor is a skill published in the GitHub repository Yuno15-bb/c-brain (2 stars, last pushed 11d ago), licensed Apache-2.0. It adds 59 tokens to every session and 292 once invoked, about $0.0003 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
potpie-debug-memory
Use while debugging or troubleshooting failures, flaky tests, incidents, production alerts, CI failures, local dev setup issues, repeated bugs, prior fixes, failed attempts, and verification history.
kip-cognitive-nexus
Persistent graph-based memory for AI agents via KIP (Knowledge Interaction Protocol). Provides retrieval-first memory operations (KQL), durable writes (KML), schema discovery (META), and memory hygiene patterns. Use whenever the agent needs to consult or update persistent memory, especially for: remembering user…
chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
memesh
Use MeMesh to remember, recall, and manage AI knowledge across sessions, and to exchange task-focused messages with local agents. Triggers when the user asks to remember something, recall past decisions, forget outdated info, learn from mistakes, analyze work patterns, contact another agent, or handle a memeshmessage…
memesh-review
Review and optimize the MeMesh memory database. Analyzes health score, finds stale/conflicting/redundant memories, shows work patterns, and suggests cleanup actions. Use when asked to "review memories", "check memory health", "clean up knowledge", or "what's in my memory".
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.