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 skills/leekjay/claude-skills-plugin/code-quality-standardsnpx skills add LeekJay/claude-skills-plugin --skill code-quality-standardsgit 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/skills/leekjay/claude-skills-plugin/code-quality-standards)<a href="https://agentmods.dev/skills/leekjay/claude-skills-plugin/code-quality-standards"><img src="https://agentmods.dev/badge/skills/leekjay/claude-skills-plugin/code-quality-standards.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.1 | $0.00057 | $0.01569 |
| Opus 5 | $0.00028 | $0.00785 |
| Sonnet 5 | $0.00011 | $0.00314 |
| Haiku 4.5 | $0.00006 | $0.00157 |
Grade A, and why
code-quality-standards 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 5d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Standards
Ensure code quality and project maintainability through standardized check workflows.
Decision Framework
Default behavior: For comprehensive code quality checks, prefer Sub-Agent mode to ensure thorough validation.
🔴 Mandatory Sub-Agent Triggers (ANY ONE triggers delegation)
- Full quality check: User requests complete code quality validation before commit/PR
- Multiple check types: Needs format + lint + typecheck + test (2+ check types)
- Fix and verify cycle: Errors found that need fixing and re-verification
- Large changeset: Changes span 5+ files or significant code modifications
- Pre-release check: Final validation before release or deployment
- CI failure investigation: Investigating why CI checks failed
- Type error fixing: Multiple type errors that need systematic fixing
- Iterative fixing: Fixes may introduce new errors requiring multiple rounds
🟢 Main Conversation Handling (ALL conditions must be met)
- Single check: Only running one command (e.g., "run lint" or "run tests")
- Quick verification: Just checking if something passes, not fixing
- Known simple fix: Already know what to fix, just need to apply it
- No iteration needed: Single pass expected to succeed
Decision Flow
Check for ANY 🔴 mandatory trigger?
├─ YES → ✅ USE SUB-AGENT MODE immediately
│ subagent_type="code-quality-standards:code-quality-checker"
└─ NO → Check if ALL 🟢 simple conditions are met?
├─ YES → Handle in main conversation
└─ NO → ✅ USE SUB-AGENT MODE (default behavior)
Quick Reference Examples
| User Description | Trigger Signal | Decision |
|---|---|---|
| "Run all quality checks" | 🔴 Full quality check | Sub-Agent |
| "Just run pnpm lint" | 🟢 Single check | Main conversation |
| "Fix all type errors" | 🔴 Type error fixing | Sub-Agent |
| "Check if tests pass" | 🟢 Quick verification | Main conversation |
| "Prepare code for PR" | 🔴 Pre-release check | Sub-Agent |
| "Run format" | 🟢 Single check | Main conversation |
| "Why is CI failing?" | 🔴 CI failure investigation | Sub-Agent |
| "I changed 10 files, please verify" | 🔴 Large changeset | Sub-Agent |
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.
- 5d ago First seen · 219 lines · 57 tokens per session scan A 731add5ca92e
code-quality-standards is a skill published in the GitHub repository LeekJay/claude-skills-plugin (4 stars, last pushed 8mo ago), licensed MIT. It adds 57 tokens to every session and 1,569 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…