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/wan-huiyan/claude-ecosystem-hygieneWrote 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/plugins/wan-huiyan/claude-ecosystem-hygiene/memory-hygiene)<a href="https://agentmods.dev/plugins/wan-huiyan/claude-ecosystem-hygiene/memory-hygiene"><img src="https://agentmods.dev/badge/plugins/wan-huiyan/claude-ecosystem-hygiene/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/plugins/wan-huiyan/claude-ecosystem-hygiene/memory-hygiene"><img src="https://agentmods.dev/badge/plugins/wan-huiyan/claude-ecosystem-hygiene/memory-hygiene.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 1mo 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
{
"name": "memory-hygiene",
"description": "Audit and clean up Claude Code's persistent memory system \u2014 MEMORY.md, memory topic files, lessons, axioms, phase templates, ADRs, and the project docs/ taxonomy.",
"version": "3.5.0",
"author": {
"name": "wan-huiyan",
"url": "https://github.com/wan-huiyan"
},
"repository": "https://github.com/wan-huiyan/claude-ecosystem-hygiene",
"license": "MIT",
"keywords": [
"claude-code",
"claude-code-skill",
"memory",
"hygiene",
"lessons",
"adr"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 166 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 20 lines scan A cb56463f3145
memory-hygiene is a plugin published in the GitHub repository wan-huiyan/claude-ecosystem-hygiene (1 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.
Other plugins, from other repositories
session-handoff
End-of-session handoff with bucket-aware dispatch across the canonical 7-bucket docs/ taxonomy (aligned with memory-hygiene v3.3), doc-freshness reverse-lint + skill-freshness audit, and future-to-do emission as GitHub issues. Captures knowledge, routes artifacts to…
llm-wiki
Build a shared Markdown knowledge base with local hybrid search and an optional evidence-linked workflow to capture task lessons, evaluate skill improvements, and apply or roll back tested changes.
chamnan
Preserves repository architecture, decisions, work state, and reusable engineering context across coding-agent sessions.
memory-loop
A memory lifecycle for Claude Code's native file-based memory: a save gate against hallucinated memories, tiered expiry (short-tier memories archived — never deleted — when they lapse), a propose-then-confirm consolidation pass (merge/dedupe long-tier memory), a correction-signal hook that logs likely corrections for…
file-lifecycle
A lifecycle for the files an agent leaves behind: a per-session scratch dir ($CLAUDESESSIONTMP) deleted after a grace period once the session ends, an opt-in age-based sweep of /.claude/tmp with a keep/ttl registry, and a long-term archive with dated names, a fail-closed secret scan, duplicate refusal and a generate.
clean-context
Keeps a project's noise out of Claude's default context: audit-context measures where the budget is going, ignore-setup applies a managed .ignore, a Glob setting, and a short read-deny list for secrets, leaving every excluded path readable on purpose.