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.
git 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/index)<a href="https://agentmods.dev/commands/404-not-found/mindlink/index"><img src="https://agentmods.dev/badge/commands/404-not-found/mindlink/index/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/commands/404-not-found/mindlink/index"><img src="https://agentmods.dev/badge/commands/404-not-found/mindlink/index.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.00000 | $0.00811 |
| Opus 5.5 | $0.00000 | $0.00324 |
| Sonnet 5.5 | $0.00000 | $0.00162 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
index 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 1mo 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MindLink CLI Reference
Full command reference for the MindLink CLI. Each command page includes synopsis, options, output examples, and error cases.
Commands
Commands are grouped by when and how you run them.
Run once — in your terminal, before first AI session
| Command | Description |
|---|---|
| init | Set up .brain/ memory for the current project |
Ask your AI to run — or run yourself in any terminal
| Command | Description |
|---|---|
| status | Show last session summary and what's next |
| summary | Full briefing — everything MindLink knows, in one view |
| log | View full session history |
| diff | Show what changed in .brain/ since the current session started |
| verify | Health check — are memory files filled in and up to date? |
Keep running in a background terminal tab (while sessions are active)
| Command | Description |
|---|---|
| sync | Watch for changes from other sessions and surface them automatically |
mindlink sync runs in watch mode by default — it stays alive and prints a notification whenever another session appends to .brain/SHARED.md. Use --once to check a single time and exit.
Launched automatically by Claude Code — not by hand
| Command | Description |
|---|---|
| mcp | Start the MindLink MCP server (stdio transport for AI tool integration) |
mindlink mcp is started automatically when Claude Code launches a session. It exposes 4 MCP tools (mindlink_read_memory, mindlink_write_memory, mindlink_session_update, mindlink_verify) for schema-validated memory reads and writes.
Run in your terminal between sessions — not via AI
These commands are interactive, change settings, or modify files. Keep human hands on them.
| Command | Description |
|---|---|
| clear | Reset SESSION.md for a fresh session start (keeps memory and history) |
| reset | Wipe all .brain/ memory back to blank templates |
| config | Change agents, git tracking, or auto-sync after init |
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.
- 1mo ago First seen · 94 lines · 0 tokens per session scan A d70340b22b2f
index is a command published in the GitHub repository 404-not-found/mindlink (10 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 811 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.
memory-store
Store an insight, decision, or pattern to memory.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
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.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.