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/stilero/claude-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/agents/stilero/claude-plugins/code-quality-analyzer)<a href="https://agentmods.dev/agents/stilero/claude-plugins/code-quality-analyzer"><img src="https://agentmods.dev/badge/agents/stilero/claude-plugins/code-quality-analyzer/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/stilero/claude-plugins/code-quality-analyzer"><img src="https://agentmods.dev/badge/agents/stilero/claude-plugins/code-quality-analyzer.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.00047 | $0.00658 |
| Opus 5.5 | $0.00019 | $0.00263 |
| Sonnet 5.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 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.
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.
- 1mo ago 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 3mo ago), licensed MIT. It adds 47 tokens to every session and 658 once invoked, about $0.0002 per session on Opus 5.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
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.