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/melodic-software/claude-code-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/melodic-software/claude-code-plugins/claude-config)<a href="https://agentmods.dev/plugins/melodic-software/claude-code-plugins/claude-config"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/claude-config/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/melodic-software/claude-code-plugins/claude-config"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/claude-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
claude-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 14d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- harness-config — 89% identical, 7 lines differ
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "claude-config",
"version": "0.55.5",
"description": "Nine configuration-health skills (plus setup) for a repo's Claude Code configuration: audit (settings.json / .mcp.json / hooks / plugins / permissions drift), audit-automation-gaps (evidence-gated verdicts on automation gaps), audit-permission-grants (allow-rule / allowed-tools grants for auto-mode durability and portability), audit-permission-state (the permission rules actually in effect: every settings scope merged with per-rule provenance, what auto mode drops on entry, config written where nothing reads it, and which managed intents are enforced versus loosenable), draft-auto-mode-rules (interview and draft a paste-ready autoMode classifier block; prints only, never writes), audit-instructions (locally-owned instruction surfaces vs current model capability, proposing removals/rewrites of instructions the model no longer needs, and detecting cross-surface instruction conflicts), audit-prompting-postures (the additive lane: posture guidance the prompting guide says a component's purpose needs but the component does not carry), audit-pass (one coordinated, ordered, resumable pass over a named target: three-scope inventory, run-time-derived exclusion set, stable finding identity, suppression memory, resume, one human gate, delegating every check to the plugin that owns it), and unhobble (the empirical bare-baseline experiment: reversibly strip a repo's standing instructions, log real stumbles against the current model, re-add only what evidence earns).",
"author": {
"name": "Melodic Software",
"email": "[email protected]"
},
"license": "MIT",
"keywords": [
"settings",
"configuration",
"hooks",
"plugins",
"permissions",
"automation",
"audit",
"maintenance",
"skill",
"instructions"
]
}
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.
- 14d ago Changed 0af3673372f5
- 15d ago Changed df0c004c2dcc
- 16d ago Changed c3b61c54e5da
- 17d ago Changed 1a6859e5113f
- 18d ago Changed 22aa8c34cdbf
- 20d ago Changed 5f30c61484da
- 21d ago Changed f001f0af8584
- 22d ago Changed 283e0dcd0123
- 23d ago Changed c667369a8b4e
- 24d ago First seen · 24 lines scan A 9c4dfdb19075
claude-config is a plugin published in the GitHub repository melodic-software/claude-code-plugins (25 stars, last pushed today), 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
error-therapist
Audit and rewrite error messages to be helpful and actionable.
oslog
Read, stream, and analyze Apple unified logs (OSLog) for iOS/macOS apps.
debug-triage
Tight cause-fix-test triage from a pasted error or stack trace. No lectures, no bullet-point philosophy -- just cause, fix, regression test, sibling files to update.
heal
A maintenance workflow for diagnosing failures and criticism, fixing their underlying causes, and reducing the chance that they happen again.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.