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.
npx agentmods add agents/kenspc/kenspc-claude-plugin/bug-reviewergit 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.svg" alt="Measured on agentmods" 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 | $0.00057 | $0.00923 |
| Opus 5 | $0.00028 | $0.00462 |
| Sonnet 5 | $0.00011 | $0.00185 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
bug-reviewer 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 3d 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.
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.
- 3d 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 1mo ago), with no licence file. It adds 57 tokens to every session and 923 once invoked, about $0.0003 per session on Opus 5. 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 agents, from other repositories
namba-designer
Use this role when art direction, palette/tone logic, composition, motion intent, or generic-looking UI surfaces need to be clarified before implementation or review. State effect: read-only. Do not edit repository files.
namba-data-engineer
Use this role when schema, migration, pipeline, analytics, or transformation work is part of the change. State effect: workspace-write. Edit only files assigned by the main session.
auth-wiring-specialist
Use when wiring auth into a new project, switching auth providers, or adding role/org features. Carries the factory's auth conventions — the provider decision matrix (Better Auth + orgs primary, Supabase + RLS for RLS-heavy cases, Clerk for consumer/SSO), the unified requireAuth / requireRole / withOrgContext wrapper…
verification-engineer
Use to design the verification strategy for a change — what would prove it correct, given its blast radius, and what is currently unverifiable. Read-only — outputs a verification plan and a gap list, not a review and not code. Sister to code-reviewer (which finds defects in a diff) and the generalization of…
session-reviewer
Analyze conversation patterns to detect recurring frustrations, corrections, and problematic tool usage. Feeds findings into practices/inbox/ or CLAUDEERRORS.md. Use after long sessions or when /forge insights triggers analysis.
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.