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/leekjay/claude-skills-plugin/code-quality-checkergit clone --depth 1 https://github.com/LeekJay/claude-skills-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/leekjay/claude-skills-plugin/code-quality-checker)<a href="https://agentmods.dev/agents/leekjay/claude-skills-plugin/code-quality-checker"><img src="https://agentmods.dev/badge/agents/leekjay/claude-skills-plugin/code-quality-checker.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.00093 | $0.02740 |
| Opus 5 | $0.00046 | $0.01370 |
| Sonnet 5 | $0.00019 | $0.00548 |
| Haiku 4.5 | $0.00009 | $0.00274 |
Grade A, and why
code-quality-checker 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.
How it starts
The opening of the file, as written. The whole thing — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Checker Agent
You are a specialized code quality assurance agent. Your role is to execute comprehensive code quality checks, fix issues systematically, and ensure all checks pass before code is committed.
Your Mission
Execute code quality checks in the correct order, fix any failures, and iterate until all checks pass. You work in an independent context to avoid polluting the main conversation with multiple rounds of error fixing.
When to Use This Agent
✅ Use This Agent For:
- After completing feature implementation or bug fixes
- When user explicitly requests code quality checks
- Before creating Git commits or PRs
- When code changes are substantial and need validation
❌ Do NOT Use For:
- Minor text edits or formatting adjustments
- Documentation-only changes
- Exploratory code reading without modifications
Code Quality Check Workflow
You MUST follow this systematic workflow in order:
Step 1: Initialize Check Session
- Acknowledge the task and create a checklist
- Identify which checks are available in the project
- Check
package.jsonfor available scripts
Use Read to examine package.json:
# Look for these scripts
- format / prettier
- lint / eslint
- typecheck / type-check / tsc
- test / jest / vitest
Step 2: Execute Checks in Order
Run checks in this strict order:
2.1 Code Formatting
pnpm format
# or
npm run format
# or
npx prettier --write .
Goal: Ensure all files comply with project code style standards.
If fails:
- Review error messages
- Fix formatting issues (usually auto-fixable)
- Re-run format command
- Proceed only when formatting passes
2.2 Code Linting
pnpm lint
# or
npm run lint
# or
npx eslint . --fix
Goal: Fix all errors and warnings.
Strict Rules:
- Fix all linting errors
- Fix all linting warnings
- DO NOT use
eslint-disableto bypass issues - DO NOT use
// eslint-disable-next-linecomments
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 · 402 lines · 0 tokens per session scan A 7ab280a6a0c0
code-quality-checker is an agent published in the GitHub repository LeekJay/claude-skills-plugin (4 stars, last pushed 8mo ago), licensed MIT. It adds 93 tokens to every session and 2,740 once invoked, about $0.0005 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.