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/bugs)<a href="https://agentmods.dev/plugins/melodic-software/claude-code-plugins/bugs"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/bugs/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/bugs"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/bugs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bugs 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": "bugs",
"version": "0.13.0",
"description": "Produces from an informal defect description a structured five-field bug report: title, steps to reproduce, expected vs actual, severity with justification, and suggested fix location. Read-only by default: it emits the report and never edits code, opens a PR, or files an issue on its own.",
"author": {
"name": "Melodic Software",
"email": "[email protected]"
},
"license": "MIT",
"keywords": [
"bug",
"bugs",
"defect",
"scan",
"bug-hunting",
"triage",
"issue",
"workflow",
"skill"
],
"userConfig": {
"output_dir": {
"type": "directory",
"title": "Output directory",
"description": "Where --file writes reports. When unset, reports go to the plugin's own persistent data directory. Set this to a path in your repository if you want bug reports committed alongside your code."
}
}
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 283 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 3a9eb2caed39
- 2d ago Changed fdda45d62d0d
- 4d ago Changed a96f82cc75e6
- 8d ago Changed 8ae4978480bc
- 11d ago Changed 61e8ee23e3ad
- 12d ago Changed · -1 lines 56139a32cc06
- 13d ago Changed d65312688fe7
- 14d ago Changed e8ed3d748ea4
- 15d ago Changed 680ac557e8de
- 16d ago First seen · 30 lines scan A dfbf038955e7
bugs 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.