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/mcpgit clone --depth 1 https://github.com/404-not-found/mindlinkWhat 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.00877 |
| Opus 5 | $0.00000 | $0.00439 |
| Sonnet 5 | $0.00000 | $0.00175 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
mcp 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 3d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mindlink mcp
Start the MindLink MCP server for AI tool integration.
Synopsis
mindlink mcp
Description
mindlink mcp starts a local Model Context Protocol server over stdio. It exposes 4 tools that AI agents (like Claude Code) can call to read and write memory with schema validation and structured responses.
This command is launched automatically by Claude Code — you do not need to run it yourself. When you run mindlink init and select Claude Code, MindLink adds the MCP server entry to .claude/settings.json so Claude Code starts it on every session.
Why MCP?
- Schema-validated writes — the AI can't accidentally overwrite the wrong section
- Structured reads — returns only the sections needed for the current task (token-efficient)
- Verify loop — the AI can call
mindlink_verify()after writing to confirm the write succeeded
Tools
mindlink_read_memory(section?)
Read a section of this project's MEMORY.md.
- No argument: returns Core + User Profile only (the recommended default at session start)
- With section: returns just that section
| Section value | Content |
|---|---|
Core |
Project identity, stack, top decisions |
Architecture |
System design decisions |
Decisions |
Key choices made and why |
Conventions |
Team patterns and coding standards |
User Profile |
Personal facts about the user |
Important Context |
Business context, deadlines, preferences |
mindlink_write_memory(section, content)
Append a fact or decision to a section of MEMORY.md.
Never overwrites existing content — always appends. Always include a <!-- added: YYYY-MM-DD --> timestamp in the content.
mindlink_session_update(summary)
Overwrite SESSION.md with a summary of the current session.
Call this as the last action of every response. SESSION.md is temporary; it gets cleared between sessions. MEMORY.md is permanent.
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.
- 3d ago First seen · 127 lines · 0 tokens per session scan A 62f874b58213
mcp 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 877 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.