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/uninstallgit 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.00473 |
| Opus 5 | $0.00000 | $0.00236 |
| Sonnet 5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
uninstall 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mindlink uninstall
Remove MindLink from the current project.
Run in your terminal only — this permanently removes files. Always prompts for confirmation first.
Synopsis
mindlink uninstall [--yes]
Description
Removes everything MindLink created in this project directory:
.brain/folder and all memory files inside it- Agent instruction files (
CLAUDE.md,CURSOR.md, etc.) that were created duringmindlink init .claude/settings.jsonhook (if Claude was one of the configured agents)
The MindLink CLI itself is not removed. To uninstall the CLI globally:
npm uninstall -g mindlink
MindLink reads config.json inside .brain/ to know which agent files to remove. If config is unreadable, it removes all known agent files as a safe default.
Options
| Flag | Description |
|---|---|
--yes, -y |
Skip confirmation and remove everything immediately |
Examples
mindlink uninstall # interactive — shows what will be removed, asks to confirm
mindlink uninstall --yes # skip confirmation (useful in scripts)
What Gets Removed
.brain/ (all memory files)
CLAUDE.md (if Claude was configured)
CURSOR.md (if Cursor was configured)
AGENTS.md (if Codex was configured)
GEMINI.md (if Gemini was configured)
.github/copilot-instructions.md (if Copilot was configured)
.windsurfrules (if Windsurf was configured)
.clinerules (if Cline was configured)
CONVENTIONS.md (if Aider was configured)
.claude/settings.json (if Claude was configured)
What Stays
- The mindlink CLI itself
- Any files MindLink did not create
Error: Not Initialized
✗ No .brain/ found in this directory.
Nothing to uninstall here.
Related Commands
mindlink init— set up memory for this projectmindlink reset— wipe memory but keep MindLink installed
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 · 89 lines · 0 tokens per session scan A d303bb04e8c6
uninstall 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 473 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.