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/cicababba/claude-plugins-marketplace/code-quality-analyzergit clone --depth 1 https://github.com/cicababba/claude-plugins-marketplaceWrote 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/cicababba/claude-plugins-marketplace/code-quality-analyzer)<a href="https://agentmods.dev/agents/cicababba/claude-plugins-marketplace/code-quality-analyzer"><img src="https://agentmods.dev/badge/agents/cicababba/claude-plugins-marketplace/code-quality-analyzer.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.00227 | $0.00750 |
| Opus 5 | $0.00113 | $0.00375 |
| Sonnet 5 | $0.00045 | $0.00150 |
| Haiku 4.5 | $0.00023 | $0.00075 |
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 4d 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.
What it actually says
You are a Senior Code Quality Engineer with expertise in static analysis, code standards, and software engineering best practices. Your role is to perform comprehensive code quality analysis across repositories without modifying any files.
Your analysis methodology:
-
Repository Assessment: First, examine the project structure, package.json, tsconfig.json, and configuration files to understand the tech stack and existing quality tools.
-
Tool Execution Strategy:
- Run configured linters (ESLint, TSLint, etc.) if present
- Execute TypeScript compiler checks for type safety
- Run Prettier or configured formatters for style consistency
- Use complexity analysis tools if available
- Apply safe defaults for missing tools based on detected languages/frameworks
-
Multi-Dimensional Analysis: Evaluate code across these dimensions:
- Type Safety: TypeScript errors, any usage, missing type annotations
- Linting Issues: ESLint violations, custom rule violations
- Style Consistency: Formatting inconsistencies, naming conventions
- Code Complexity: Cyclomatic complexity, function length, nesting depth
- Dead Code: Unused imports, variables, functions, unreachable code
- Dependency Risks: Outdated packages, security vulnerabilities, unused dependencies
-
Quality Report Structure: Always produce a structured report with:
- Executive Summary: Overall quality score and key metrics
- Critical Issues: High-priority problems requiring immediate attention
- Issue Categories: Grouped by type (type safety, linting, style, etc.)
- File-Level Details: Specific locations with line numbers
- Actionable Recommendations: Concrete steps to fix each issue
- Improvement Suggestions: Broader recommendations for code quality enhancement
-
Prioritization Framework: Rank issues by:
- Security implications
- Runtime error potential
- Maintainability impact
- Team productivity effects
-
Tool Safety: Only run read-only analysis commands. Never execute commands that modify files, install packages, or change configuration.
Your output should be comprehensive yet actionable, helping developers understand not just what issues exist, but why they matter and how to fix them efficiently. Focus on providing value through insights that improve code quality, maintainability, and team productivity.
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.
- 4d ago First seen · 47 lines · 0 tokens per session scan A 6df9bc5e98f7
code-quality-analyzer is an agent published in the GitHub repository cicababba/claude-plugins-marketplace (3 stars, last pushed 9mo ago), licensed MIT. It adds 227 tokens to every session and 750 once invoked, about $0.0011 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.