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 paruff/uFawkesAI --skill code-qualitygit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/paruff/ufawkesai/code-quality)<a href="https://agentmods.dev/skills/paruff/ufawkesai/code-quality"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/code-quality.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.00030 | $0.00704 |
| Opus 5 | $0.00015 | $0.00352 |
| Sonnet 5 | $0.00006 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
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 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Code Quality Validation
Load trigger:
"load code-quality skill"> DORA: Cap 5 (Small Batches / Shift Left on Quality) Token cost: Low
Purpose
Validate code quality, formatting, and maintainability.
Responsibilities
- Run linters
- Run formatters (check mode, not fix)
- Validate naming conventions
- Validate directory structure
- Validate test coverage
Inputs
- Build output (source code)
Outputs
code-quality.json
Validation Rules
Linting
- Lint passes with no errors
- Lint warnings documented (if any)
- No new lint warnings introduced
Formatting
- Code formatted per project conventions
- No formatting diffs in review
- Consistent indentation and style
Naming Conventions
- Variables/functions use project convention (camelCase, snake_case)
- Classes/Types use PascalCase
- Constants use UPPER_SNAKE_CASE or project convention
- File names follow project convention
Directory Structure
- Files in correct directories per architecture
- Test files co-located or in test directory per convention
- No files in wrong layer
Type Safety
- No
anytypes (or justified with comment) - No
@ts-ignoreor@ts-expect-errorwithout justification - No
type: ignore(Python) without justification - Proper type exports
Code Smells
- No dead code left in place
- No commented-out code blocks
- No TODO without issue number
- No magic numbers or strings
Tools
| Language | Linter | Formatter |
|---|---|---|
| TypeScript | ESLint | Prettier |
| Python | Ruff / Flake8 | Black |
| Go | golangci-lint | gofmt |
| Rust | clippy | rustfmt |
Output Format
{
"skill": "code-quality",
"status": "pass | fail",
"lint": {
"status": "pass | fail",
"errors": 0,
"warnings": 2,
"details": ["Unused import at src/utils.ts:5"]
},
"formatting": {
"status": "pass | fail",
"diffs": 0
},
"naming": {
"status": "pass | fail",
"violations": []
},
"type_safety": {
"status": "pass | fail",
"any_count": 0,
"ts_ignore_count": 0
}
}
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 · 119 lines · 30 tokens per session scan A b3d30e88b3ca
code-quality is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 14d ago), licensed MIT. It adds 30 tokens to every session and 704 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
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
coverage
Compute code coverage for active track or module. Targets 95%+ coverage with report and justification for uncovered lines. Complements TDD workflow.
template-formal
Strongly-typed multiagent ant-robot colony exemplar — ADTs, session-typed protocols, affine-discipline resource handles, storage-as-functor framing, Active-Inference-flavored decision loop, mypy-as-oracle negative controls.
template-test-creation
Create pytest suites under the no-mocks policy — real data, temp files, subprocess, pytest-httpserver. USE WHEN adding tests, raising coverage, testing new src/ module, or user forbids mocks.
Unit Test Improver
Reviews existing unit tests for gaps, weak assertions, and missing edge cases, then rewrites them to be more robust.
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.