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/configgit 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.00417 |
| Opus 5 | $0.00000 | $0.00209 |
| Sonnet 5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
config 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.
What it actually says
mindlink config
Change settings for the current project after init.
Run in your terminal — this opens an interactive menu. Not suitable for AI to run on your behalf.
Synopsis
mindlink config
Description
Opens an interactive menu to change any setting that was configured during mindlink init. All settings are stored in .brain/ and scoped to the current project path.
Settings
Git tracking
Controls whether .brain/ is committed to git or ignored.
| Option | What it does |
|---|---|
| Enable | Removes .brain/ from .gitignore. Your team shares the same AI memory. |
| Disable | Adds .brain/ to .gitignore. Memory stays on your machine only. |
Auto-sync
Controls whether mindlink sync runs automatically in the background.
| Option | What it does |
|---|---|
| Enable | Sync runs automatically. Sessions stay in sync without manual intervention. |
| Disable | You run mindlink sync manually when you want to sync. |
Agent instruction files
Add or remove agent instruction files for this project. Same multi-select menu as mindlink init.
Selecting an agent that isn't already set up generates its instruction file. Deselecting an agent that exists prompts you to confirm before deleting the file.
Examples
mindlink config
Interactive Menu
Current settings · /Users/yuanhong/projects/my-app
Git tracking : enabled (team shares memory)
Auto-sync : enabled (watch mode)
Agent files : CLAUDE.md, CURSOR.md, AGENTS.md ...
? What would you like to change?
❯ Git tracking
Auto-sync
Agent instruction files
Exit
Related Commands
mindlink init— initial setup (first time only)mindlink sync— manually run sync
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 · 82 lines · 0 tokens per session scan A c4c9dd78c800
config 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 417 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.