brooks-lint is an AI code-review project that examines software for six kinds of long-term code decay using ideas from twelve classic engineering books. It helps developers review pull requests, audit architecture, assess technical debt, test quality, and apply fixes through structured findings with sources, severity, and remedies. Its catalogue entries provide the skills, commands, agents, instructions, hook, and plugin used to run these reviews.
Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add hyhmrright/brooks-lint/plugin install brooks-lintWrote 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/commands/hyhmrright/brooks-lint/brooks-test)<a href="https://agentmods.dev/commands/hyhmrright/brooks-lint/brooks-test"><img src="https://agentmods.dev/badge/commands/hyhmrright/brooks-lint/brooks-test.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.00008 | $0.00065 |
| Opus 5 | $0.00004 | $0.00032 |
| Sonnet 5 | $0.00002 | $0.00013 |
| Haiku 4.5 | $0.00001 | $0.00006 |
Grade A, and why
brooks-test 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 8d 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.
What it actually says
Read ${CLAUDE_PLUGIN_ROOT}/skills/brooks-test/SKILL.md and follow its instructions exactly. If that file cannot be found, locate the brooks-test skill's SKILL.md in this plugin and follow it.
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.
- 8d ago First seen · 6 lines · 8 tokens per session scan A 04b759cd366f
brooks-test is a command published in the GitHub repository hyhmrright/brooks-lint (1,455 stars, last pushed 6d ago), licensed MIT. It adds 8 tokens to every session and 65 once invoked, about $0.0000 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-30.
Other commands, from other repositories
tdd
Test-driven development with tests that actually catch breaks: red before green, name the break each test catches, and the mutation check before done.
ci
CI/CD hygiene and run health: pinned actions, timeouts, concurrency, tests — plus the latest runs via gh.
test
Run the repository's actual test suite: every ecosystem's canonical runner — NOT run is never green.
converge
Run an unattended review→fix→re-review loop on the current branch until the reviewer has no findings at or above Medium, then push once. Findings stay in a local scratch file and are never posted to GitHub. Stops early on oscillation, a red test suite, or a 4-review cap.
review
Review the current git diff — auditor selected by --mode (general, security, a11y, deps, perf, tests, contributor-trust, ux) or auto-inferred from the diff when omitted. Pass a PR number to review a specific PR; use --check-followup to re-check a PR after the owner has addressed feedback.
debug
Diagnose a bug, failing test, or unexpected behavior — root-cause first, minimal fix, regression test. Performance-shaped symptoms (slow, latency, profiling) are routed to workflow-performance-investigation via one clarifying question.