verify

A command-line health check for MindLink's project memory files. It checks whether the memory contains useful information, recent session state, required files, and a manageable amount of content.

In plain words
What is it for?
Use it to review memory quality before ending a session, optionally as structured JSON or with a repair option.
Why use it?
It helps reveal when the assistant's memory is empty, missing, stale, or too large to be useful.

Command

Install

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.

agentmods
npx agentmods add commands/404-not-found/mindlink/verify
Clone the repo
git clone --depth 1 https://github.com/404-not-found/mindlink
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 960 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00960
Opus 5 $0.00000 $0.00480
Sonnet 5 $0.00000 $0.00192
Haiku 4.5 $0.00000 $0.00096

Measured 2d ago against content hash c651da437eb2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

verify 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.

commands/verify.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Check that .brain/ memory is healthy and up to date.


Synopsis

mindlink verify [--json] [--fix]

Description

Runs a health check on the current project's .brain/ directory. Answers: "is my AI's memory in good shape right now?"

Unlike mindlink doctor (which checks setup correctness), mindlink verify checks content quality — whether memory files are actually filled in, whether the AI is actively writing session state, and whether MEMORY.md is getting too large to be useful.

Your AI can run this. Ask it to run mindlink verify to check its own work before closing a session.


Checks

Check Pass Warn Fail
Core section Has real content Empty or placeholder only
User Profile Has real content Empty or placeholder only
SESSION.md freshness Updated < 3 days ago 3–7 days > 7 days
LOG.md present Exists Missing
MEMORY.md size < 100 real lines 100–200 lines > 200 lines
Agent files All present Some missing None present

Output

  ◉ MindLink Verify
  /Users/you/my-project

  ✓  Core section — filled
  ✓  User Profile — filled
  ⚠  SESSION.md — last updated 5 days ago
       SESSION.md is getting stale...
  ✓  LOG.md — 14 sessions logged
  ✗  MEMORY.md — 217 lines (target: under 200)
       Run mindlink prune to consolidate stale entries.
  ✓  Agent files — all 2 present

  1 error, 1 warning.
  Run mindlink verify --fix to auto-repair 0 issues.

Options

Flag Description
--json Output results as JSON — useful for scripting or AI consumption
--fix Auto-fix recoverable issues (regenerate missing agent files)

--fix Behavior

Auto-fix only applies to recoverable issues. It never touches user-written memory content.

Check --fix action
agent_files missing Re-generate from current templates
core / user_profile empty Print actionable message — no auto-fill
memory_size too large Print actionable message — run mindlink prune
session_fresh stale No auto-fix — AI must update SESSION.md

Read the full file on GitHub · 123 lines

Changes

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.

  1. 2d ago First seen · 123 lines · 0 tokens per session scan A c651da437eb2

Subscribe to this mod's changes

verify 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 960 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.