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/claude-plugin-repo-ci-release)<a href="https://agentmods.dev/plugins/wan-huiyan/claude-ecosystem-hygiene/claude-plugin-repo-ci-release"><img src="https://agentmods.dev/badge/plugins/wan-huiyan/claude-ecosystem-hygiene/claude-plugin-repo-ci-release/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/claude-plugin-repo-ci-release"><img src="https://agentmods.dev/badge/plugins/wan-huiyan/claude-ecosystem-hygiene/claude-plugin-repo-ci-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
claude-plugin-repo-ci-release 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 11d 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": "claude-plugin-repo-ci-release",
"description": "Wire up CI validation and automatic release-cutting for a Claude Code plugin or marketplace repo (one with a .claude-plugin/marketplace.json and plugins/*). Adds two GitHub Actions — a structure validator on every PR/push, and a release-on-version-bump job that cuts a GitHub Release whenever VERSION changes — plus the bundled validator script and workflow templates. Use when a plugin repo has no CI or its GitHub Releases have drifted behind the shipped version.",
"version": "1.0.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",
"plugin-repo",
"ci",
"github-actions",
"release-automation",
"ecosystem-hygiene"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 308 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.
- 11d ago First seen · 18 lines scan A 9c281d4e04ac
claude-plugin-repo-ci-release is a plugin published in the GitHub repository wan-huiyan/claude-ecosystem-hygiene (1 stars, last pushed 25d 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
beecount-release
A release workflow for BeeCount projects that coordinates version tags, change logs, website updates and video copy across two code repositories. A release is the process of publishing a new software version.
handbook-glab
GitLab CLI (glab) expertise for managing merge requests, issues, CI/CD pipelines, and repositories from the command line.
ship
Complete PR workflow from commit to production with validation.
nyann
Project governance for Claude Code. Bootstrap and maintain git workflow, hooks, commits, releases, CI, docs, and repo health.
release-conductor
Owns everything around the diff: craft Conventional Commits and PR descriptions, recommend the right semver bump by reasoning about behavioral breaking changes, assemble changelogs from messy history, and guide merge-conflict resolution, rebase planning, and git-history archaeology.
skrrt
Every skrrt skill in one bundle for the skills.sh CLI — git shipping workflow, structured markdown authoring with auto-fixed lint-clean output, subagent orchestration, and self-documenting code discipline. Claude Code installs per bucket instead; see marketplace.json.