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.
/plugin marketplace add clever-cc-plugins/cc-confignpx agentmods add plugins/clever-cc-plugins/cc-config/cc-configgit clone --depth 1 https://github.com/clever-cc-plugins/cc-configGrade A, and why
cc-config 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 yesterday.
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": "cc-config",
"description": "Bootstrap and audit a best-practice Claude Code configuration",
"version": "1.2.3",
"author": {
"name": "Michael van Laar"
},
"homepage": "https://github.com/clever-cc-plugins/cc-config",
"repository": "https://github.com/clever-cc-plugins/cc-config",
"license": "MIT"
}
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.
- yesterday First seen · 12 lines scan A 72f5224e0092
cc-config is a plugin published in the GitHub repository clever-cc-plugins/cc-config (1 stars, last pushed 6d 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
cc-content
Content creation skills for marketing projects — brand onboarding, LinkedIn posts, blog articles, sample curation, session management, and skill authoring.
coder-eval
Test whether your Claude Code skills actually trigger, and benchmark any coding agent — author, run, and analyze the eval suite that proves it, locally or as a CI gate.
infino-ai
Plugin marketplace listing 1 plugin: code-context.
sound
Code taste as installable rules. Probe a repo's stack, select only the rules its code shows a surface for (evidence-cited per rule), confirm, and scaffold a browsable .claude/sound/ rule map (surfaced by the sound:prime skill). Installed rules are user-owned; re-runs reconcile.
rudder
Maintain a device-local spec from coding-session intent, then generate focused unit tests with your existing coding agent.
neatcontext
Save Claude Code work as reusable, domain-aware context.