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/404-not-found/mindlink/doctorgit clone --depth 1 https://github.com/404-not-found/mindlinkWrote 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/404-not-found/mindlink/doctor)<a href="https://agentmods.dev/commands/404-not-found/mindlink/doctor"><img src="https://agentmods.dev/badge/commands/404-not-found/mindlink/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 | $0.00000 | $0.00631 |
| Opus 5 | $0.00000 | $0.00316 |
| Sonnet 5 | $0.00000 | $0.00126 |
| Haiku 4.5 | $0.00000 | $0.00063 |
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 4d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mindlink doctor
Check that your MindLink setup is healthy.
Run in your terminal. Use this when something feels off, after a fresh import, or just to verify everything is wired up correctly.
Synopsis
mindlink doctor
Description
Runs a series of checks on your project's MindLink setup and reports any problems. Exits with code 1 if any critical issues are found, 0 if everything is healthy (warnings are allowed).
What Gets Checked
| Check | What it looks for |
|---|---|
.brain/ |
Exists in the current directory |
config.json |
Present and valid JSON |
MEMORY.md |
Core section has content; warns if getting too long |
SESSION.md |
Has content and shows when it was last updated |
LOG.md |
Session count, last session date, how far back history goes |
| Agent files | Each configured agent's instruction file exists |
| Claude hook | .claude/settings.json hook is present and valid |
Output
◉ MindLink Doctor
/Users/yuanhong/my-app
✓ .brain/ found
✓ config.json valid
✓ MEMORY.md Core has content
✓ SESSION.md — updated 2 hours ago
✓ LOG.md — 12 sessions logged (last: Apr 10, 2026, going back to: Jan 5, 2026)
✓ CLAUDE.md — Claude Code
✓ CURSOR.md — Cursor
✓ .claude/settings.json — UserPromptSubmit hook active
· .brain/ is committed to git (shared team memory)
All good. Your AI has a healthy brain.
Warning example
! MEMORY.md Core is getting long
Consider asking your AI to consolidate — Core is read on every session start.
1 warning, no critical issues. Your AI will still work.
Failure example
✗ MEMORY.md missing
Run mindlink init to recreate it.
1 problem found — fix the issues above and re-run mindlink doctor.
Exit Codes
| Code | Meaning |
|---|---|
0 |
Healthy (warnings allowed) |
1 |
One or more critical problems found |
When to Run
- After
mindlink import— verify the import landed correctly - When your AI seems confused or isn't reading context — check the agent files
- On a new machine after cloning — make sure instruction files are in place
- Periodically to catch drift before it becomes a problem
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.
- 4d ago First seen · 99 lines · 0 tokens per session scan A c153018dbad6
doctor is a command published in the GitHub repository 404-not-found/mindlink (11 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 631 tokens. 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 commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
neo-review
Get Neo's code review with semantic matching against past findings in memory. Use on a diff or module before merge, especially where earlier mistakes in this codebase are likely to recur. Skip for formatting, lint-catchable issues, and single-line changes.