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/repo-hygiene)<a href="https://agentmods.dev/plugins/wan-huiyan/claude-ecosystem-hygiene/repo-hygiene"><img src="https://agentmods.dev/badge/plugins/wan-huiyan/claude-ecosystem-hygiene/repo-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/repo-hygiene"><img src="https://agentmods.dev/badge/plugins/wan-huiyan/claude-ecosystem-hygiene/repo-hygiene.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
repo-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 12d 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": "repo-hygiene",
"description": "Pre-PR checklist and repo cleanup for data-science / analytics projects. Catches mistakes that cost hours later: data files committed to git (.csv/.db/.parquet), hardcoded /Users/ paths, tracked runtime artifacts, branch-ownership confusion, internal docs drifting from deliverables, and client data in public repos. The project-quality track's 'clean' tool — sibling to test-effectiveness-auditor (which measures the same repo's tests). Use before gh pr create, before merging, or at handover.",
"version": "1.2.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",
"repo-hygiene",
"pre-pr-checklist",
"cleanup",
"data-files",
"project-quality"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 204 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.
- 12d ago First seen · 21 lines scan A df4ad6225c0c
repo-hygiene is a plugin published in the GitHub repository wan-huiyan/claude-ecosystem-hygiene (1 stars, last pushed 26d 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
handbook-git-worktree
Git worktree management for working on multiple branches simultaneously.
handbook-glab
GitLab CLI (glab) expertise for managing merge requests, issues, CI/CD pipelines, and repositories from the command line.
issue-to-pr
Take a GitHub issue (bare, or tracked on a Project board) from triage to a merge-ready PR through a gated, worktree-isolated pipeline that scales its depth to the task and asks at most one batched question. The gates hold every run: design hardening, tests green, code review clean. Once you approve the PR in-session…
agent-traffic-control
Coordination toolkit for parallel Claude Code sessions sharing one repo — issue-pickup claim protocol (assignee + wip label), worktree & session-isolation pitfalls, parallel-PR conflict recovery, subagent-integrity edge cases, and squash/merge mechanics for parallel-PR workflows. Plus resume-gate, an opt-in hook that…
commit
Generate a commit message from staged changes, then let the user review before committing in manual mode or commit without confirmation in auto mode. Use when the user wants to commit changes or create a git commit.
misuzu
Respond to PR review comments semi-automatically. Splits review findings into logical units, fixes and commits them one by one, then replies and resolves review threads.