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 ccplugins/awesome-claude-code-pluginsnpx agentmods add plugins/ccplugins/awesome-claude-code-plugins/bug-detectivegit clone --depth 1 https://github.com/ccplugins/awesome-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/ccplugins/awesome-claude-code-plugins/bug-detective)<a href="https://agentmods.dev/plugins/ccplugins/awesome-claude-code-plugins/bug-detective"><img src="https://agentmods.dev/badge/plugins/ccplugins/awesome-claude-code-plugins/bug-detective.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
bug-detective 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.
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:
- bug-detective — 100% identical, 0 lines differ
What it actually says
{
"name": "bug-detective",
"description": "Systematically debug issues with step-by-step troubleshooting approaches.",
"version": "1.0.0",
"author": {
"name": "Anonymous"
},
"homepage": "https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/bug-detective"
}What it installs
The manifest is a name and a version. 1 command travel with it, and installing the plugin installs all of them — 7 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.
- 2d ago First seen · 9 lines scan A e65936510ece
bug-detective is a plugin published in the GitHub repository ccplugins/awesome-claude-code-plugins (931 stars, last pushed 24d ago), licensed Apache-2.0. 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
problem-solver-specialist
Universal expert problem-solving agent specializing in complex debugging, mysterious runtime behavior, integration issues, and multi-layered technical challenges across any technology stack or project type. Uses advanced research methodologies including GitHub issues mining, Perplexity deep research, community…
double-check
An easy way to force agent to think again if it's statement that the "Job is done and production ready" is actually done - usually it's not. Thanks to this command you don't have to check after the agent if they did their job.
fix-github-issue
Analyzes and fixes GitHub issues using a structured approach with GitHub CLI for issue details, implementing necessary code changes, running tests, and creating proper commit messages.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
debug-session
Ask Claude Code to help you debug an issue.
optimize
Analyze and optimize code performance.