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/mathiasbourgoin/roster/code-quality-auditornpx skills add mathiasbourgoin/roster --skill code-quality-auditorgit clone --depth 1 https://github.com/mathiasbourgoin/rosterWrote 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/mathiasbourgoin/roster/code-quality-auditor)<a href="https://agentmods.dev/skills/mathiasbourgoin/roster/code-quality-auditor"><img src="https://agentmods.dev/badge/skills/mathiasbourgoin/roster/code-quality-auditor.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.00021 | $0.00937 |
| Opus 5 | $0.00010 | $0.00468 |
| Sonnet 5 | $0.00004 | $0.00187 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
code-quality-auditor 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Auditor
Check implementation against knowledge base properties and conventions. Uses only built-in tools (grep, wc, read) — no external linters required.
Steps
1. Load KB References
- Read
kb/properties.mdfor invariants, constraints, and quality thresholds. - Read
kb/glossary.mdfor canonical naming conventions and term definitions. - Read
kb/spec.mdfor architectural boundaries and module responsibilities. - Read
kb/architecture.md(top-level and per-module, if present) for declared structural expectations — module boundaries, dependency direction, layering. Check code structure against them; a divergence is a finding (cite file:line), and expectations that are not statically verifiable are noted as such, never assumed satisfied.
2. Check: Function Size
- Scan source files for function/method definitions.
- Measure line count per function (use grep + wc approach).
- Flag functions exceeding the threshold defined in
properties.md(default: 50 lines if not specified). - Exclude test files from size checks unless properties.md says otherwise.
3. Check: DRY Violations
- Search for duplicated code blocks (identical or near-identical sequences of 5+ lines).
- Look for repeated patterns: duplicated error handling, copy-pasted validation logic, repeated configuration blocks.
- Flag each duplication with both locations.
4. Check: Naming Consistency with Glossary
- For each term in
kb/glossary.md, search the codebase for variant spellings, abbreviations, or synonyms. - Example: if glossary defines "Transaction", flag code using "tx", "txn", "trans" inconsistently.
- Check that type names, function names, and module names use glossary-canonical forms.
5. Check: Invariant Preservation
- For each invariant in
kb/properties.md, verify the code maintains it:- If an invariant says "X is never null", search for code paths where X could be null.
- If an invariant says "Y is always called before Z", trace call sequences.
- If an invariant says "all inputs are validated", check for unvalidated entry points.
- This is best-effort static analysis — flag suspicious patterns, don't claim proof.
What ships with it
1 file 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.
- 4d ago First seen · 103 lines · 21 tokens per session scan A ff0f5b152023
code-quality-auditor is a skill published in the GitHub repository mathiasbourgoin/roster (2 stars, last pushed 9d ago), licensed MIT. It adds 21 tokens to every session and 937 once invoked, about $0.0001 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…
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…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…