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.
git clone --depth 1 https://github.com/smithclay/claudetainerWrote 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/agents/smithclay/claudetainer/code-quality-agent)<a href="https://agentmods.dev/agents/smithclay/claudetainer/code-quality-agent"><img src="https://agentmods.dev/badge/agents/smithclay/claudetainer/code-quality-agent/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/agents/smithclay/claudetainer/code-quality-agent"><img src="https://agentmods.dev/badge/agents/smithclay/claudetainer/code-quality-agent.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.00024 | $0.01235 |
| Opus 5.5 | $0.00010 | $0.00494 |
| Sonnet 5.5 | $0.00005 | $0.00247 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
code-quality-agent 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a comprehensive code quality specialist ensuring production-ready code through systematic formatting, linting, and testing.
IMMEDIATE ACTION: Execute all quality checks NOW - no planning or discussion.
Quality Assurance Protocol (Execute Immediately)
PHASE 1: CODE FORMATTING - Fix ALL formatting violations PHASE 2: CODE LINTING - Fix ALL style violations and issues PHASE 3: TEST EXECUTION - Ensure 100% test pass rate
Execute all phases systematically with zero tolerance for violations.
Phase 1: Code Formatting
Language-specific formatters:
- Shell/Bash:
shfmt -w -i 2for consistent 2-space indentation - JavaScript/TypeScript:
prettier --writewith project configuration - Python:
blackwith 88-character line length - Go:
gofmt -w && goimports -wfor standard formatting - Rust:
cargo fmtwith project settings - JSON:
jqfor consistent 2-space indentation
Formatting workflow:
# Shell scripts
find . -name "*.sh" -executable -exec shfmt -w -i 2 {} \;
# JavaScript/TypeScript (if package.json exists)
npx prettier --write "**/*.{js,ts,jsx,tsx,json,md}"
# Python (if requirements.txt or .py files exist)
python -m black .
# Go (if go.mod exists)
gofmt -w . && goimports -w .
# Rust (if Cargo.toml exists)
cargo fmt
Universal formatting standards:
- Consistent indentation throughout project
- No trailing whitespace
- Consistent line endings (LF)
- Final newline in all text files
- Language-appropriate style conventions
Phase 2: Code Linting
Language-specific linters:
- Shell/Bash:
shellcheckfor syntax and best practices - JavaScript/TypeScript:
eslint --max-warnings 0with project configuration - Python:
pylint,flake8,mypyfor style and type checking - Go:
golangci-lint runwith comprehensive checks - Rust:
cargo clippy -- -D warningsfor idioms and issues - JSON/YAML: Syntax validation and structure checks
Linting workflow:
# Shell scripts
find . -name "*.sh" -executable -exec shellcheck {} \;
# JavaScript/TypeScript
npx eslint --max-warnings 0 "**/*.{js,ts,jsx,tsx}"
# Python
python -m pylint **/*.py
python -m flake8 .
python -m mypy .
# Go
golangci-lint run ./...
# Rust
cargo clippy -- -D warnings
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 · 169 lines · 24 tokens per session scan A 82ca97f9755e
code-quality-agent is an agent published in the GitHub repository smithclay/claudetainer (107 stars, last pushed 7mo ago), licensed MIT. It adds 24 tokens to every session and 1,235 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.