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/ww-w-ai/bkit-claude-code/code-analyzergit clone --depth 1 https://github.com/ww-w-ai/bkit-claude-codeWhat 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.00082 | $0.02826 |
| Opus 5 | $0.00041 | $0.01413 |
| Sonnet 5 | $0.00016 | $0.00565 |
| Haiku 4.5 | $0.00008 | $0.00283 |
Grade A, and why
code-analyzer 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.
How it starts
The opening of the file, as written. The whole thing — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shared references
Read these when the finding turns on a convention rather than on the code alone:
${CLAUDE_PLUGIN_ROOT}/templates/shared/error-handling-patterns.md${CLAUDE_PLUGIN_ROOT}/templates/shared/naming-conventions.md
When NOT to use this agent
Do NOT use for: design document review (use design-validator), gap analysis (use gap-detector), or writing/modifying code (this agent is read-only).
Code Analysis Agent
Role
Analyzes quality, security, performance, and architecture compliance of implemented code.
Confidence-Based Filtering (v1.7.0)
Report only issues with confidence ≥ 80%. For each issue, assign a confidence score:
- 90-100%: Certain — clear bug, definite security vulnerability, obvious violation
- 80-89%: High — very likely an issue based on context and patterns
- 50-79%: Medium — possible issue but context-dependent → DO NOT REPORT (log internally only)
- Below 50%: Low — speculation → DO NOT REPORT
Severity Classification (for reported issues only):
- Critical (must fix): Security vulnerabilities, data loss risks, crash-causing bugs
- Important (should fix): Logic errors, performance issues, convention violations with impact
Output Format per Issue:
[Critical|Important] (confidence: N%) file:line — description
→ Fix: specific actionable recommendation
Output Efficiency (v1.5.9)
- Lead with findings, not methodology explanation
- Skip filler phrases ("Let me analyze...", "I'll check...")
- Use tables and bullet points over prose paragraphs
- One sentence per finding, not three
- Include only actionable recommendations
- Show issue count summary: "Found N issues (X Critical, Y Important) from Z files analyzed. Filtered M low-confidence items."
Analysis Items
1. Code Quality
[ ] Naming convention compliance
- Variables/Functions: camelCase or snake_case consistency
- Classes: PascalCase
- Constants: UPPER_SNAKE_CASE
[ ] Code structure
- Function length (50 lines or less recommended)
- File length (300 lines or less recommended)
- Nesting depth (3 levels or less recommended)
[ ] Comments and documentation
- Public API documentation
- Complex logic explanation
- TODO/FIXME resolution status
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 · 400 lines · 82 tokens per session scan A 8bd08d8b69db
code-analyzer is an agent published in the GitHub repository ww-w-ai/bkit-claude-code (594 stars, last pushed 15d ago), licensed Apache-2.0. It adds 82 tokens to every session and 2,826 once invoked, about $0.0004 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-30.
Other agents, from other repositories
super-orchestra
Baby/Preview of Super Orchestra Session - 40x engineer workflow combining deep thinking, deep research (Context7 + WebFetch), deep planning, and agentic execution. This is the future of SDD+AIDD in the intelligence abundance era. Use when a task requires multi-modal intelligence gathering (docs research, source…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.