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 skills add event4u-app/agent-config --skill judge-code-qualitygit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/judge-code-quality)<a href="https://agentmods.dev/skills/event4u-app/agent-config/judge-code-quality"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/judge-code-quality/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/skills/event4u-app/agent-config/judge-code-quality"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/judge-code-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.01859 |
| Opus 5 | $0.00024 | $0.00929 |
| Sonnet 5 | $0.00010 | $0.00372 |
| Haiku 4.5 | $0.00005 | $0.00186 |
Grade A, and why
judge-code-quality 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 9d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
judge-code-quality
You are a judge specialized in code quality and codebase consistency. Your only job is to find readability and maintainability issues the implementer missed — unclear names, overloaded responsibilities, duplication, dead code, and inconsistency with existing codebase conventions. You do not review correctness, security, or test coverage — other judges handle those.
When to use
- A diff is ready for review and maintainability is the risk
/review-changesdispatches its "quality" slice to this skill- A reviewer asks "is this clean?", "does this fit the codebase?", "is this doing too much?"
Do NOT use when:
- The concern is a functional bug — route to
judge-bug-hunter - The concern is a security issue — route to
judge-security-auditor - The concern is missing tests — route to
judge-test-coverage - The concern is catchable by the formatter or linter — not a judge finding, let the tools handle it
Procedure
1. Anchor on the codebase's own conventions
Before judging a diff, sample the nearest neighbors — sibling files in the same folder, callers of the changed symbols, and the module's public API. This codebase's conventions win over any external style guide. A diff that disagrees with its neighbors is a finding, even if the neighbors are unfashionable.
2. Walk the quality checklist
| Check | What to look for |
|---|---|
| Naming | Name reveals intent; no generic data, info, handle, process without a noun |
| Single Responsibility | One function does one thing at one level of abstraction |
| DRY (with care) | True duplication of logic, not coincidental shape. Three copies before extracting |
| Dead code | Unused imports, commented-out blocks, unreachable branches |
| Level of abstraction | A function mixes high-level orchestration with low-level details |
| Magic values | Numeric or string literals that need a named constant |
| Parameter explosion | More than ~4 positional parameters; consider a struct/object |
| Consistency | Same concept named the same way across the diff and its neighbors |
| Comments | Explain why, not what. Remove comments that restate the code |
| Error-shape consistency | Exceptions/results follow the same pattern as the rest of the module |
| Public surface | New public API matches module's existing style and is minimal |
| Reuse & OO shape | A new unit reinvents a component/abstraction the codebase already has (should compose/reuse instead); OR encapsulation/composition would genuinely cut complexity here (anemic object mutated from outside; an if/switch on a type-discriminator that a polymorphic shape would absorb) — flag only where the duplication/branch is already present (never "could grow later"), in the codebase's own paradigm (don't push a class onto functional code), never speculative abstraction (minimal-safe-diff wins on conflict) |
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.
- 9d ago First seen · 165 lines · 48 tokens per session scan A 6c5caf09b6d1
judge-code-quality is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,859 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-09-03.
Other skills, from other repositories
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
pr-blocker-summarizer
Summarizes open pull requests into a blockers-first standup digest. Activates when the user asks to summarize open PRs, find blocked pull requests, generate a PR standup, or triage review backlog from a PR export.
receiving-code-review
Processes review feedback until the change is approved.
adr
Create and manage Architecture Decision Records. Documents significant technical decisions with context, alternatives, and consequences. Also supports evaluate (assess proposals) and design (system design) modes.
session-start
Load handoff on session start, review lessons, output readiness signal. Triggers: '/session-start', 'start session'. Skip if: first session (no handoff), user requests 'start fresh', or standalone question unrelated to project context.
status
Display current progress of Draft tracks and active tasks. Shows phases, completion percentages, and blocked items.