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/cubha/claude-workflow-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/cubha/claude-workflow-plugins/debugger)<a href="https://agentmods.dev/plugins/cubha/claude-workflow-plugins/debugger"><img src="https://agentmods.dev/badge/plugins/cubha/claude-workflow-plugins/debugger/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/cubha/claude-workflow-plugins/debugger"><img src="https://agentmods.dev/badge/plugins/cubha/claude-workflow-plugins/debugger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
debugger 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 1mo 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.
What it actually says
{
"name": "debugger",
"version": "1.0.0",
"description": "Log-driven debugging workflow: insert logs, pinpoint the root cause, fix, verify, and clean up. --pw mode auto-reproduces web UI bugs via a bundled Playwright MCP. Supports JS/TS, Python, Java, and Kotlin.",
"author": {
"name": "cubha"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 171 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.
- 1mo ago First seen · 9 lines scan A 49b8ae3c529e
debugger is a plugin published in the GitHub repository cubha/claude-workflow-plugins (2 stars, last pushed 2mo 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
power-automate
Build, edit, run, and debug Power Automate cloud flows via the FlowAgent MCP server — connection lifecycle, surgical edits, copy across environments, run management, and validated expressions.
dead-code
Find and remove dead code, unused imports, and duplicates across any language.
log-correlation
Correlates and troubleshoots logs across OS, AWS, application, and web server sources. Extensible via log-types/ definitions.
codeweb
See what your AI edits affect. Structural checks for AI code changes. Local call/import graphs and 28 MCP tools for impact, callers, and duplication. No LLM in the checks.
cw-debug
Generic CloudWatch log investigation skill with adaptive debugging methodology.
dive-deeper
Deep-dive analysis skill for planning phase — trace execution paths, find related code, surface edge cases and potential problems.