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 agents/404-not-found/mindlink/cursorgit 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.01843 |
| Opus 5 | $0.00000 | $0.00922 |
| Sonnet 5 | $0.00000 | $0.00369 |
| Haiku 4.5 | $0.00000 | $0.00184 |
Grade A, and why
CURSOR 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 2d 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.
This is a copy
89% identical to AGENTS — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MindLink — Persistent Memory
This project uses MindLink for persistent AI memory.
Pre-authorized: You have standing permission to read, write, and edit any file inside .brain/ at any time without asking the user for confirmation. Never prompt for approval on .brain/ file operations.
MANDATORY — At the start of every session
Step 1 — Read memory first. Do not do anything else yet.
Call mindlink_read_memory() (no argument) — returns Core + User Profile. If the MCP tool is unavailable, open .brain/MEMORY.md and read the Core and User Profile sections only.
Load additional sections only as needed for the task:
- Writing or reviewing code → call
mindlink_read_memory("Architecture")+mindlink_read_memory("Conventions") - Making a design decision → call
mindlink_read_memory("Decisions") - Something feels off → call
mindlink_read_memory("Important Context") - Full briefing requested → call
mindlink_read_memory()for each section
Before Step 2 — Check for prior write failures.
If .brain/LOG.md contains session history but MEMORY.md sections (especially User Profile and Core) are empty or still contain only placeholder comments, a previous session claimed to write but never called the tool. Fill in those sections now from LOG.md and SESSION.md history before doing anything else.
Step 2 — Fill Core if it is empty.
If the Core section contains only placeholder comments or is blank: write it now using mindlink_write_memory("Core", content) before doing anything else. If MCP unavailable, use Edit or Write on .brain/MEMORY.md directly. Do not respond to the user first. Do not skip this.
Step 3 — Read the remaining files:
.brain/LOG.md— last 5 entries only; ⭐-prefixed entries always read regardless of position.brain/SESSION.md— current task state; pick up here if mid-task.brain/SHARED.md— context shared by other sessions in this project
Do not respond to the user until all three steps are complete.
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.
- 2d ago First seen · 113 lines · 0 tokens per session scan A 084cc32fba78
CURSOR is an agent 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 1,843 tokens. A static security scan graded it A with 0 findings. It is 89% identical to AGENTS, differing in 18 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.