spring-clean

Install

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.

Security

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 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.

spring-clean/.claude-plugin/plugin.json · 10 lines

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"
  }
}

Changes

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.

Related

Other plugins, from other repositories