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/kenspc/kenspc-claude-pluginWrote 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/agents/kenspc/kenspc-claude-plugin/bug-reviewer)<a href="https://agentmods.dev/agents/kenspc/kenspc-claude-plugin/bug-reviewer"><img src="https://agentmods.dev/badge/agents/kenspc/kenspc-claude-plugin/bug-reviewer/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/agents/kenspc/kenspc-claude-plugin/bug-reviewer"><img src="https://agentmods.dev/badge/agents/kenspc/kenspc-claude-plugin/bug-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00091 | $0.03213 |
| Opus 5.5 | $0.00036 | $0.01285 |
| Sonnet 5.5 | $0.00018 | $0.00643 |
| Haiku 4.5 | $0.00009 | $0.00321 |
Grade C, and why
bug-reviewer scanned grade C with 1 finding 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 today.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
no cleanup, while files left in `/tmp` or removed with `rm -rf` depend on the The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- today Changed · +1 lines 39f5e346a5d8
- 2d ago Changed · +24 lines · +31 tokens per session 1c378c5298ec
- 3d ago Changed · +11 lines f58b8c80e9f9
- 21d ago Changed · +3 lines 1fac4a794860
- 24d ago Changed · +12 lines ac1b6f45c93d
- 25d ago Changed · +99 lines · +3 tokens per session scan A → C 2d7a0d6c5c23
- 1mo ago First seen · 99 lines · 57 tokens per session scan A a3139394c996
bug-reviewer is an agent published in the GitHub repository kenspc/kenspc-claude-plugin (1 stars, last pushed today), with no licence file. It adds 91 tokens to every session and 3,213 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
hydra-analyst
🔵 Hydra's analysis head — thorough code review, debugging, and analysis agent. Use proactively whenever Claude needs to review code for quality, analyze a bug with error messages or stack traces, evaluate dependencies, assess test coverage, review pull request changes, identify performance issues, or analyze…
reviewer
Read-only review of a diff or PR for correctness, security, performance and maintainability. Returns path:line findings and a verdict. Use before merging a change.
security-auditor
Delegate for security-focused analysis: scanning for secrets, vulnerabilities, auth gaps, dependency risks, and compliance issues. Use before any deployment or when touching auth/crypto/data-handling code.
code-reviewer
PROACTIVELY use after code changes to review for security, performance, correctness, and maintainability. Reads diffs, analyzes patterns, reports issues by severity. Does not modify code.
debugger
Adversarial post-implement sweep agent. Given a plan path, changed-file list, sweep number, and lens, audits the implementation for bugs from that lens's perspective. Flag-only — never modifies code. Scope bounded to changed files + 2-hop dependencies. One finding per real issue; no style/naming/formatting feedback.
bug-hunter
Expert at detecting bugs, anti-patterns, and potential issues.