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/diffgit 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.00798 |
| Opus 5 | $0.00000 | $0.00399 |
| Sonnet 5 | $0.00000 | $0.00160 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
diff 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mindlink diff
Show what changed in .brain/ since the current session started.
Synopsis
mindlink diff [--since <ref>] [--json]
Description
Shows a per-file summary of .brain/ changes since the session began — which files were modified, how many lines they contain, and when they were last touched.
If .brain/ is committed to git, mindlink diff also shows line-level additions and removals so you can see exactly what the AI wrote.
This command is useful for:
- Verifying that your AI actually wrote to MEMORY.md during the session (not just claimed to)
- Reviewing what context was captured before closing a session
- Debugging why a follow-up session is missing context
Your AI can run this. Ask it to run mindlink diff to check its own work.
Output
Without git tracking:
.brain/ changes
Session started 12m ago
.brain/ is not git-tracked — showing modification times only
● MEMORY.md 94 lines · modified 3m ago
○ SESSION.md 32 lines · modified 12m ago
○ LOG.md 24 lines · modified 12m ago
○ SHARED.md 21 lines · modified 12m ago
✓ 1 file updated this session.
● = modified this session · ○ = not modified this session
With git tracking (.brain/ committed):
.brain/ changes
Session started 12m ago
Git diff against: HEAD~1
● MEMORY.md 97 lines · modified 3m ago
+ TypeScript + Node.js <!-- added: 2026-04-12 -->
+ Use mtime-based session verification for Stop hook
○ SESSION.md 32 lines · modified 12m ago
no changes since last commit
Options
| Flag | Description |
|---|---|
--since <ref> |
Git ref or date to diff against. Default: HEAD~1. Examples: HEAD~3, "2026-04-10" |
--json |
Output as JSON — useful for scripting or AI consumption |
Examples
Check what changed this session:
mindlink diff
Diff against 3 commits ago:
mindlink diff --since HEAD~3
Machine-readable output:
mindlink diff --json
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 · 116 lines · 0 tokens per session scan A b4961ac54afc
diff 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 798 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.