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/smk-labs/claude-pluginsWrote 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/smk-labs/claude-plugins/spring-clean)<a href="https://agentmods.dev/plugins/smk-labs/claude-plugins/spring-clean"><img src="https://agentmods.dev/badge/plugins/smk-labs/claude-plugins/spring-clean/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/smk-labs/claude-plugins/spring-clean"><img src="https://agentmods.dev/badge/plugins/smk-labs/claude-plugins/spring-clean.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
spring-clean 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": "spring-clean",
"description": "Two passes over a repo. spring-clean measures against a declared scoreboard, deletes or gitignores what does not belong, relocates dev docs, notes, clones and dumps to a <project>-workspace repo, splits oversized files, draws package boundaries and writes its plan to a numbered unit list that survives a dead context. workspace-rules then gives that repo its rules at both layers, sorting each by what it hands the model: information it cannot infer is told where a session starts, anything a script could count is counted as a linter setting, an architecture test or a hook proved red by name and green on an untouched tree, and the cap, the displacement clause and the dated judged-out list go inside the check file itself.",
"version": "3.0.0",
"author": {
"name": "Seyed M. Keramati",
"url": "https://github.com/SMKeramati"
}
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 158 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 · 10 lines scan A 55802c8f309f
spring-clean is a plugin published in the GitHub repository smk-labs/claude-plugins (11 stars, last pushed 20d 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-30.
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.
review-pr
Review PRs in a Tour Guide (expository) or Adversarial (audit) posture, with logical file ordering, context, and severity-rated findings. Forge-agnostic (GitHub + Bitbucket).
axiom-git
Composes Conventional Commits messages with gitmoji from the staged diff, deciding type, scope, emoji, subject, and body, and gating on protected branches, staged secrets, and pre-commit hooks.
commit-helper
Generate conventional commit messages and pull requests with approval workflow.
branch-recap
Tells you what your branch actually changed — what was done, why, and what deserves a second look, instead of the diff — then files the fixes into the commits they belong to.