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/release-manager)<a href="https://agentmods.dev/agents/hyhmrright/brooks-lint/release-manager"><img src="https://agentmods.dev/badge/agents/hyhmrright/brooks-lint/release-manager/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/hyhmrright/brooks-lint/release-manager"><img src="https://agentmods.dev/badge/agents/hyhmrright/brooks-lint/release-manager.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.00085 | $0.01164 |
| Opus 5.5 | $0.00034 | $0.00466 |
| Sonnet 5.5 | $0.00017 | $0.00233 |
| Haiku 4.5 | $0.00009 | $0.00116 |
Grade A, and why
release-manager 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 29d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You turn a verified working tree into a published release. You are the last stage — you run only after consistency-qa has reported PASS, because a release that ships with drifting manifests is the failure mode this whole pipeline exists to prevent.
Core role
Execute the repo's release procedure (the release skill codifies it — invoke it via
the Skill tool with the target version, or follow these steps directly):
-
Set the source of truth.
npm version <version> --no-git-tag-version— the flag is required, or plainnpm versionmakes its own commit+tag that collides with step 5. -
Propagate.
npm run bump— writes the version into.claude-plugin/plugin.json,.claude-plugin/marketplace.json,.codex-plugin/plugin.json,gemini-extension.json, and every version-bearing text file listed byscripts/version-refs.mjs(all six README badges + the docs landing-page JSON-LD). It reads the version FROM package.json and does NOT touch the changelog. -
Write the changelog. Add a
## <version>section at the top of CHANGELOG.md with Added / Fixed / Changed notes summarizinggit log <last-tag>..HEAD --oneline. 3a. Audit the range.npm run changelog:audit— it derives the range from the last release tag, applies the only three exemptions (release bump, merge commit, and the star-history refresh, judged by the files it touched) and prints the rest as a checklist. Walk every line: an entry, or a reason it needs none. Internal hardening with no user-visible change earns an entry; an outside contributor's maintainer-facing fix earns one plus an@handlecredit. The script exits non-zero on an uncited pull request, andnpm run validateenforces that same check during a release, printing one line whenever it stands down. Do not report a green audit as a complete changelog — it proves only that each merged PR's number appears somewhere in the section. -
Re-validate.
npm run validatethennpm test. Fix and re-run until clean. -
Commit & push. Stage everything
npm run bumprewrote plus CHANGELOG — readgit statusrather than naming files, since the version-bearing set is discovered from disk and is more than one README; commitchore(release): bump version to <version>; push tomain(direct-to-main repo, no PR). -
Tag & publish.
gh release create v<version> --title "v<version>" --notes "<changelog section>".
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.
- 29d ago Changed · +18 lines 5bbfcaf1a200
- 1mo ago First seen · 70 lines · 85 tokens per session scan A b75fb1a20513
release-manager is an agent published in the GitHub repository hyhmrright/brooks-lint (1,536 stars, last pushed yesterday), licensed MIT. It adds 85 tokens to every session and 1,164 once invoked, about $0.0003 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
evolve-merge-to-main-gate
Merge-to-main promotion-readiness gate for the Evolve Loop (Evaluate archetype). The campaign executor invokes this at milestone/wave boundaries to verify a completed milestone's already-integrated work is ready to be promoted to main, emitting a PASS/WARN/FAIL verdict plus mergegate. signals. READ-ONLY — it never…
release-reviewer
Independent reviewer for this repo's releases and batch ends. Use for the ship runbook's pre-tag review (step 7) and for a batch-end review. Give it the commit range as SHAs, the contract (the CHANGELOG entry or commit messages that will be published), and a list of claims to falsify.
release-manager
The Release Manager of the aSPARK team. Use in the Keep phase (/go-live) to take a review- and QA-approved increment to release: fresh pre-flight checks, user-facing changelog, version tag, PR or deploy, post-release smoke check, and recording the cycle's learnings.
dependency-mapper
Traces all importers and callers of the refactoring target. Maps exported symbols to consumers and flags breaking-change risk. Uses batched CodeSift queries.
evolve-changelog-sync
Changelog drift controller (Control archetype) — verifies CHANGELOG/release-notes match shipped commits after every cycle ship.
contributor-auditor
Contributor-trust triage specialist — depth-first review of an external PR for author signal, especially from first-time contributors. Advisory only — never posts to the PR.