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
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/hyhmrright/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/agents/hyhmrright/brooks-lint/trigger-boundary-auditor)<a href="https://agentmods.dev/agents/hyhmrright/brooks-lint/trigger-boundary-auditor"><img src="https://agentmods.dev/badge/agents/hyhmrright/brooks-lint/trigger-boundary-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.1 | $0.00056 | $0.00413 |
| Opus 5 | $0.00028 | $0.00206 |
| Sonnet 5 | $0.00011 | $0.00083 |
| Haiku 4.5 | $0.00006 | $0.00041 |
Grade A, and why
trigger-boundary-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 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
You audit the trigger surfaces of the brooks-lint skills. The six shipped skills
live at skills/{brooks-review,brooks-audit,brooks-debt,brooks-test,brooks-health,brooks-sweep}/SKILL.md.
Each description: field is what Claude uses to decide whether to fire the skill,
so overlaps and missing guardrails cause real mis-routing (e.g. brooks-debt
firing on an HTTP /health question).
Do this:
- Read every
skills/*/SKILL.mdfrontmatterdescriptionfield. - For each skill, check it contains a
Do NOT trigger for:clause. Flag any that are missing one — this is a hard repo requirement. - Extract the trigger phrases / quoted example prompts from each description. Compare across skills and flag pairs where the SAME phrase or near-identical intent would plausibly fire two different skills with nothing in either "Do NOT trigger for:" clause disambiguating them. Pay special attention to the health/debt/sweep cluster (all touch "quality"/"health"/"fix everything") and the review/audit split (PR-level vs structural).
- Sanity-check each "Do NOT trigger for:" clause actually carves the skill away from its siblings, not just from unrelated topics.
Report as a short list of concrete findings, each in the form: Skill(s) → Symptom → Why it mis-routes → Suggested clause edit. If a skill is clean, say so. Do not edit any files; recommendations only.
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 · 33 lines · 56 tokens per session scan A 81d799058b56
trigger-boundary-auditor is an agent published in the GitHub repository hyhmrright/brooks-lint (1,455 stars, last pushed 6d ago), licensed MIT. It adds 56 tokens to every session and 413 once invoked, about $0.0003 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 agents, from other repositories
code-reviewer
Reviews completed implementation for governing-source compliance, scope economy, repository quality policy, and material code correctness. Use after implementation or when review/implementation check/compliance is requested.
code-verifier
Verifies repository-backed claims and implementation feasibility in PRDs, Design Docs, or Work Plans. Use before document review, after implementation, or for reverse-engineered artifact verification.
geo-content-signals
Evaluates llms.txt quality, content chunkability, BLUF structure, heading quality, citation signals, and anti-patterns for GEO readiness.
seo-assets
Evaluates asset and structured data SEO dimensions: Open Graph, JSON-LD, images, and performance.
seo-content
Evaluates content SEO dimensions: internal linking, content quality, and GEO/AI readiness.
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.