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 skills add Magnifico4625/locus --skill memory-auditgit clone --depth 1 https://github.com/Magnifico4625/locusWrote 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/skills/magnifico4625/locus/memory-audit)<a href="https://agentmods.dev/skills/magnifico4625/locus/memory-audit"><img src="https://agentmods.dev/badge/skills/magnifico4625/locus/memory-audit.svg" alt="Measured on agentmods" 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.00047 | $0.00164 |
| Opus 5 | $0.00023 | $0.00082 |
| Sonnet 5 | $0.00009 | $0.00033 |
| Haiku 4.5 | $0.00005 | $0.00016 |
Grade A, and why
memory-audit 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 8d 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
Show a detailed Locus data audit using the memory_audit MCP tool.
What to do
- Call the
memory_audittool (no parameters) - Present the audit report clearly:
- Capture level
- Structural map (files, exports, imports)
- Semantic memory (count, tokens)
- Episodic memory (count, sessions, tokens)
- Hook captures (count, capture mode)
- DB and log file sizes
- Security status (secrets detected or not)
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.
- 8d ago First seen · 18 lines · 47 tokens per session scan A 8ffba7628197
memory-audit is a skill published in the GitHub repository Magnifico4625/locus (14 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 164 once invoked, about $0.0002 per session on Opus 5. 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 skills, from other repositories
memory-audit
An entry point for reviewing and maintaining an AI agent's stored memories. It describes how to remove repetition, preserve useful reasoning, and update memories when old conclusions no longer fit.
memory-audit-belief-duel
A guided review process for conflicting beliefs or memories. It examines cases where two conclusions cannot both be true, including conflicts between a general rule and a more specific memory.
memory-audit-discoverability
A review guide for checking whether stored memories can be found at the right time. It focuses on where memories are attached, when they are triggered, whether aliases are missing, and whether a parent has too many children.
memory-audit-pattern-extraction
A method for investigating repeated mistakes by comparing related memories and checking whether an earlier reminder failed. It looks at where the reminder was stored, when it was created, and whether it was strong enough to prevent the mistake.
init-workspace-documentation
Skill "init-workspace-documentation" from griddynamics/rosetta, covering agent memory.md, agent memory, preventive rules, what worked and what failed.
handover
Use when wrapping up or capturing the current state of a coding session — writes a short, dated entry to the repo's RepoHandover.md so a future agent or you can resume without grepping archived sessions. Triggers on "handover", "hand off", "write handover", "capture state", "checkpoint this session".