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 xonovex/platform --skill code-quality-guidegit clone --depth 1 https://github.com/xonovex/platformWrote 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/xonovex/platform/code-quality-guide)<a href="https://agentmods.dev/skills/xonovex/platform/code-quality-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/code-quality-guide/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/xonovex/platform/code-quality-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/code-quality-guide.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.00098 | $0.00690 |
| Opus 5.5 | $0.00039 | $0.00276 |
| Sonnet 5.5 | $0.00020 | $0.00138 |
| Haiku 4.5 | $0.00010 | $0.00069 |
Grade A, and why
code-quality-guide 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code-Quality Audit
A read-only pass over existing code: find smells, grade them by severity, report, and route each smell to the one skill that owns its definition and fix. It changes nothing.
Essentials
- Read the project's own standards first:
AGENTS.md/POLICY.md/ linked guidelines and the linter config decide what counts as a violation, not generic best-practice - Robustness is this skill's own dimension: type safety, validation, error handling, logging at boundaries, complexity, see references/robustness.md
- Route every other smell to its owner: the catalog maps each smell to a detector signal and the skill that owns it, see references/smell-catalog.md
- Keep cleanup inventories read-only: preserve functional comments and rationale; detect prose debt and other cleanup candidates, see references/comment-inventory.md and references/cleanup-inventories.md
Gotchas
- This skill is a read-only detector and grader. It names a smell and routes to the owner (oop-guide for OO-design smells, connascence-guide for coupling smells); it does not redefine or fix them.
- "Dead code" detection misses code reached via dynamic dispatch, reflection, or external entry points: verify before flagging for deletion.
- A single-implementation interface is not automatically over-engineering. It may exist for testability or a planned variant.
- Preserve comments that explain a non-obvious why, invariant, workaround, or caveat; flag restatements and plan or provenance narration.
- The "application / class / method-level" smell grouping is an informal label, not a citable taxonomy: the smell catalog groups by design-problem family instead.
- Log at boundaries and on error paths, validate at trust boundaries: "everywhere" is noise and wasted work, not robustness.
Progressive Disclosure
- Read references/robustness.md - Load when auditing robustness: type safety, validation, error handling, logging, complexity
- Read references/smell-catalog.md - Load when mapping a smell to its detector signal and owning skill (oop-guide / connascence-guide / here)
- Read references/comment-inventory.md - Load when inventorying redundant, stale, narrative, commented-out, directive-like, or ambiguous comments and docstrings
- Read references/cleanup-inventories.md - Load when inventorying barrels, duplicated shared candidates, or TODO/FIXME clusters
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 32 lines · 98 tokens per session scan A befde42a019c
code-quality-guide is a skill published in the GitHub repository xonovex/platform (6 stars, last pushed 4d ago), licensed MIT. It adds 98 tokens to every session and 690 once invoked, about $0.0004 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-09-08.
Other skills, from other repositories
gh-cli-github
List/create PRs, issues, releases, and CI run status via the gh CLI.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
review
Adversarial fresh-context review and risk check of an increment before it ships; every finding cites path:line and is re-verified. Use for "review", "qa", "quality check", "critique this".
tech-debt-ci-review
Codex adapter for deep technical-debt and CI-stability audits. Use when asked to find test theater, flaky tests, missing or mis-scoped tests, brittle CI/toolchain behavior, structural debt blocking green PRs, or a remediation order for opencode-swarm.
software-design
This skill should be used when the user asks to "handle errors", "inject dependencies", "return Result", "make it immutable", or implements business logic or error handling.
coding-review-agent-loop
This skill lets you run the coding-review-agent-loop orchestration directly inside an interactive Claude Code session, without calling claude -p for Claude turns.