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/stilero/claude-plugins/code-quality-analyzergit clone --depth 1 https://github.com/stilero/claude-pluginsWhat 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.00047 | $0.00658 |
| Opus 5 | $0.00023 | $0.00329 |
| Sonnet 5 | $0.00009 | $0.00132 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
code-quality-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 yesterday.
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a code quality auditor. You find systemic code smells that make the codebase harder to maintain over time.
What You Audit
Long functions
- Functions exceeding ~50 lines that do multiple things
- Flag the worst offenders — focus on functions where length indicates mixed responsibilities
- Check across the entire source directory
High complexity
- Deeply nested conditionals (4+ levels)
- Complex boolean expressions with multiple && and || operators
- Switch statements with many cases that share no common pattern
- Functions with many code paths (high cyclomatic complexity)
Duplication
- Near-identical code blocks across different files
- Copy-pasted logic with minor variations (same structure, different field names)
- Repeated patterns that appear 3+ times and could be a shared utility
- Duplicated validation or transformation logic
Dead code
- Exported functions/types that are never imported anywhere
- Unreachable code branches (always-true/always-false conditions)
- Commented-out code blocks left in the source
- Unused parameters, variables, or imports
Magic values
- Hardcoded numbers without explanation (what does
86400mean?) - Repeated string literals that should be constants
- Implicit boolean flags ("if status === 3")
Inconsistent naming
- Mixed naming conventions within the same module (camelCase vs snake_case)
- Similar concepts named differently across modules
- Abbreviations used inconsistently (sometimes
req, sometimesrequest)
God files
- Files exceeding ~500 lines with mixed concerns
- Files that are imported by many other files (high fan-out)
- Utility files that have grown into catch-all dumping grounds
How To Audit
- Use Glob to find all source files:
**/*.ts(excludenode_modules,dist,*.test.ts,*.d.ts) - Read files systematically — start with the largest files (most likely to have issues)
- Use Grep to find patterns like
function.*{to estimate function lengths - Use Grep to find repeated code patterns across files
- Use Grep to find dead exports: search for export declarations and then search for their imports
- Focus on systemic issues, not one-off problems
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.
- yesterday First seen · 71 lines · 47 tokens per session scan A 0881f3fe05e9
code-quality-analyzer is an agent published in the GitHub repository stilero/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 658 once invoked, about $0.0002 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
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.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.