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/loggit 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.00385 |
| Opus 5 | $0.00000 | $0.00192 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
log 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 log
View full session history.
Synopsis
mindlink log [--all] [--limit <n>] [--since <date>] [--json]
Description
Prints the contents of .brain/LOG.md in a readable format. Shows the last 10 sessions by default. Each entry is a summary of what was done in that session, appended automatically by your AI agent at the end of each session.
Options
| Flag | Description |
|---|---|
--all |
Show the full history instead of the last 10 sessions |
--limit <n> |
Show the last N sessions (default: 10) |
--since <date> |
Show sessions from a specific date forward |
--json |
Output as JSON for scripting or tool integration |
Examples
mindlink log # last 10 sessions
mindlink log --all # full history
mindlink log --limit 20 # last 20 sessions
mindlink log --since "Apr 1" # sessions from April 1 onward
mindlink log --json # machine-readable output
Output
Showing last 10 sessions · mindlink log --all to see everything
── Apr 9, 2026 ──────────────────────────────────
Scaffolded auth module, fixed login redirect bug,
decided on JWT over sessions.
── Apr 8, 2026 ──────────────────────────────────
Set up project structure, defined DB schema,
decided on Postgres over MySQL.
...8 more sessions
Related Commands
mindlink status— quick summary of the last session onlymindlink clear— reset current session state
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 · 66 lines · 0 tokens per session scan A d1ecab3dc34c
log 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 385 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.