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 studiomeyer-io/studiomeyer-marketplace --skill memory-hygienegit clone --depth 1 https://github.com/studiomeyer-io/studiomeyer-marketplaceWrote 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/studiomeyer-io/studiomeyer-marketplace/memory-hygiene)<a href="https://agentmods.dev/skills/studiomeyer-io/studiomeyer-marketplace/memory-hygiene"><img src="https://agentmods.dev/badge/skills/studiomeyer-io/studiomeyer-marketplace/memory-hygiene/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/skills/studiomeyer-io/studiomeyer-marketplace/memory-hygiene"><img src="https://agentmods.dev/badge/skills/studiomeyer-io/studiomeyer-marketplace/memory-hygiene.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.00031 | $0.00321 |
| Opus 5.5 | $0.00012 | $0.00128 |
| Sonnet 5.5 | $0.00006 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
memory-hygiene 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
Preview Memory hygiene
The full connector has maintenance and deletion tools. Start with a read-only preview and identify the exact records before any change.
- Define the scope. For an overview, use read-only status actions such as
nex_health,nex_insights,nex_contradictionswithaction: stats, ornex_decaywithaction: stats. For a topic or entity, use focusednex_search,nex_entity_search,nex_entity_open, ornex_entity_history. - Show the saved wording or identifiers, why a duplicate, conflict, or stale entry is suspected, and the proposed action. Separate evidence from inference. Search results can be incomplete; do not call a sample an account-wide audit.
- Ask the user which records, if any, to change. Choose
nex_learn_update,nex_learn_archive,nex_entity_invalidate,nex_entity_merge, or contradiction resolution only for the selected records and supported action. - Read back the result and explain what changed, including any retained history.
Do not call nex_deduplicate for a preview: its default scan can automatically merge high-confidence entities. nex_consolidate and some other maintenance actions can also write. Never permanently delete a record without a specific request and final confirmation.
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 · 16 lines · 31 tokens per session scan A 0fff2db078c1
memory-hygiene is a skill published in the GitHub repository studiomeyer-io/studiomeyer-marketplace (2 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 321 once invoked, about $0.0001 per session on Opus 5.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-10-14.
Other skills, from other repositories
memory-protocol
A shared set of rules for using a persistent memory service across coding-agent sessions.
memory
Activate this skill when starting a new session, beginning a new task, saving knowledge, recalling past decisions, or after completing significant work. Also activate on errors to log them for pattern analysis. Relevant when the user asks about memory, past context, lessons learned, decisions history, project…
engram-digest
Seed or top up this project's Engram graph from the existing codebase — an explicit, user-invoked digestion of the current working tree into typed memory nodes (decisions, principles, cautions, problems, insights, intents). Use when the user says "digest this project", "ingest the codebase into memory", "seed the…
engram
Read and write the project's durable reasoning memory (decisions, principles, cautions, problems, insights) through the Engram MCP tools. Recall relevant memory before non-trivial work; capture only durable, high-value knowledge silently at natural stopping points; keep the graph honest (judge suspects, close answered…
session-recap
Document Claude Code sessions by extracting knowledge into cross-referenced documentation. Triggers on "recap the session", "summarize the work", or after significant code changes.
garden-tending
Tend the knowledge garden — diagnose vault health, condense project memos into project.md overviews, create/merge cross-project topics, fix broken links, archive superseded notes, extend trails. Trigger on "tend the garden", "condense", "update project overview", "check vault health", "where are we with X?", "what…