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/plugin-quality)<a href="https://agentmods.dev/plugins/melodic-software/claude-code-plugins/plugin-quality"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/plugin-quality/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/plugin-quality"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/plugin-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
plugin-quality 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "plugin-quality",
"version": "0.7.12",
"description": "Post-use behavioral audit of Claude Code plugin components: a six-step audit workflow (evidence capture, grounded mapping in a fresh subagent, blindspot pass, interactive contract lock, presence-gated review seams, work-item emit with draft+confirm) over any skill, agent, hook, command, or config you have actually used — zone-informed by context-guard snapshots when present, conservative when not.",
"author": {
"name": "Melodic Software",
"email": "[email protected]"
},
"license": "MIT",
"keywords": [
"plugin-audit",
"audit",
"review",
"quality",
"work-item",
"context-guard",
"skill"
]
}
What it installs
The manifest is a name and a version. 1 agent travel with it, and installing the plugin installs all of them — 99 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.
- yesterday Changed d78e4e565680
- 2d ago Changed f595a447c5bd
- 4d ago Changed 726f39738d82
- 6d ago Changed 21535e970138
- 7d ago First seen · 21 lines scan A 3089e8f14f16
plugin-quality is a plugin published in the GitHub repository melodic-software/claude-code-plugins (16 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-09-03.
Other plugins, from other repositories
parallel-workflows
Parallel workflow orchestration using git worktrees for concurrent Claude Code sessions.
error-therapist
Audit and rewrite error messages to be helpful and actionable.
refactoring
Safe refactoring workflows -- code smell detection, extract/rename/move patterns, migration strategies (JS to TS, CJS to ESM), and structured refactoring process.
content
Content creation and publishing: three writer+optimiser pairs (guides, features, documentation) with research-first workflows, per-content reports, and deterministic audit scoring. Feature writer+optimiser now enforce Technical-Marketing Synthesis (Rule 6: ten sub-checks including coined terminology, dropdown…
social-media
Social media engagement: LinkedIn posting and DM outreach, three-skill Reddit pipeline (audience-finder for subreddit qualification, monitor for daily opportunity scanning, post-composer for genuine non-marketing posts), X/Twitter threads, cross-platform coordination, and daily social brief.
csharp-source-generator
Skills for developing C# source generators and analyzers, including code generation, analysis, and optimization techniques.