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.
git clone --depth 1 https://github.com/eddiebelaval/squireWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/eddiebelaval/squire/memory-lint)<a href="https://agentmods.dev/commands/eddiebelaval/squire/memory-lint"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/memory-lint/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/eddiebelaval/squire/memory-lint"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/memory-lint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01364 |
| Opus 5 | $0.00000 | $0.00682 |
| Sonnet 5 | $0.00000 | $0.00273 |
| Haiku 4.5 | $0.00000 | $0.00136 |
Grade A, and why
memory-lint 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 5d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/memory-lint -- MEMORY.md Health Check
You audit Eddie's auto-memory system for staleness, contradictions, dead links, bloat, and missed connections.
Lane note (2026-07-14): the nightly memory sentinel (
~/Development/id8/observatory/sentinel.py, 09:45 launchd) now runs the mechanical subset of these checks automatically -- index integrity, orphans, signatures, staleness, census parity -- and self-heals within a narrow authority list. Use /memory-lint for INTERACTIVE deep dives: contradiction scans,--deepMemPalace cross-reference, merge-candidate judgment. Before re-reporting mechanical findings, check the sentinel's latest verdict at~/Development/id8/observatory/data/health.json.
Arguments: $ARGUMENTS
Route by Arguments
| Input | Action |
|---|---|
| (empty) | Full lint |
--quick |
Index-only lint (fast, checks MEMORY.md only) |
--fix |
Lint + auto-fix safe issues (dead links, empty files) |
--deep |
Full lint + cross-reference against MemPalace |
Setup
- Read
~/.claude/projects/-Users-eddiebelaval-Development-id8/memory/MEMORY.md - Inventory all
.mdfiles in the memory directory (recursively) - If
--deep: check MemPalace availability viamempalace status
Lint Checks
Run these checks in order. Classify each finding as ERROR, WARNING, or INFO.
1. Index Integrity (ERROR)
Scan every link in MEMORY.md ([title](path) format):
- Target file exists at the referenced path
- No duplicate entries pointing to the same file
- Every line in the index is under 150 characters (truncation rule)
- Report: dead links, duplicates, overlong entries
2. Orphan Files (WARNING)
Scan all .md files in memory/ that are NOT referenced in MEMORY.md:
- List each orphan with its type (from frontmatter) and last modified date
- Suggest: add to index, merge into existing file, or delete
- Exclude: MEMORY.md itself
3. Staleness Check (WARNING)
For each memory file, check the type field and content for time-sensitive claims:
- Project memories: Check if project status matches current reality
- Look for mentions of dates, deadlines, "this week", "target: [date]"
- If the date is >14 days ago, flag as potentially stale
- Reference memories: Check if referenced URLs/paths still exist
- File paths: verify with glob
- External systems: flag for manual check
- Feedback memories: Generally stable (skip staleness check)
- User memories: Generally stable (skip staleness check)
- Report: stale entries with suggested action (verify, update, or archive)
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.
- 5d ago First seen · 157 lines · 0 tokens per session scan A bc81c481dfa0
memory-lint is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,364 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-09-03.
Other commands, from other repositories
remember
Stores decisions, patterns, and outcomes in the MCP memory knowledge graph as entities with typed observations and relations. Supports recording architectural decisions, anti-patterns, tool preferences, workflow outcomes, and project conventions that persist across sessions. Use when saving patterns, remembering…
memory
Unified read-side memory operations including knowledge graph search, session context loading, decision timeline viewing, and Mermaid graph visualization. Subcommands: search, load, history, viz, status. Complements /ork:remember (write-side). Use when searching past decisions, loading context, or visualizing the…
paul:resume
Restore context from handoff and continue work.
context-health
Dashboard de salud del contexto activo con predicción de degradación y recomendaciones de compactación. Usa cuando el usuario dice "context health", "salud del contexto", "degradation", "compactar contexto", "context overflow", "tokens", "session health", "compact", "contexto lleno". Monitorea degrdación del contexto…
capturar
Capturar ideas y notas sin interrumpir el flujo de trabajo. Usa cuando el usuario dice "capturar idea", "quick note", "nota rápida", "grab this", "take a note", "guardar idea", "note to self", "capture thought", "I should remember", "guardar esto". Guarda en memoria persistente sin romper el contexto actual.
traspasar
Generar documento de traspaso estructurado para retomar en la próxima sesión.