brooks-test

brooks-test is a skill for Claude Code from hyhmrright/brooks-lint. It costs 161 tokens per session (389 once invoked), scanned A, original, MIT.

A test-suite review guide that examines the structure and reliability of automated software tests. It explains problems such as brittle tests, excessive mocking, misleading coverage, and slow test suites.

In plain words
What is it for?
Use it to review test files or a test directory, map the test suite, diagnose structural quality problems, and produce specific findings and recommendations.
Why use it?
It helps identify when tests give a false sense of safety or become expensive to maintain, including in older codebases.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the brooks-lint plugin — 9 skills, 6 commands, 5 agents, 1 hook shipped together

Good fit Use it to review test files or a test directory, map the test suite, diagnose structural quality problems, and produce specific findings and recommendations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hyhmrright/brooks-lint/brooks-test
About the project

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.

hyhmrright/brooks-lint · 1,462 stars · on GitHub · hyhmrright.github.io

Install

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.

Any agent
npx skills add hyhmrright/brooks-lint --skill brooks-test
Clone the repo
git clone --depth 1 https://github.com/hyhmrright/brooks-lint

Made for: Claude Code.

Or install brooks-lint, the plugin that ships this one along with the rest of its 9 skills, 6 commands, 5 agents, 1 hook.

Wrote 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.

agentmods badge for brooks-test

README.md
[![agentmods](https://agentmods.dev/badge/skills/hyhmrright/brooks-lint/brooks-test/github.svg)](https://agentmods.dev/skills/hyhmrright/brooks-lint/brooks-test)
Your own site
<a href="https://agentmods.dev/skills/hyhmrright/brooks-lint/brooks-test"><img src="https://agentmods.dev/badge/skills/hyhmrright/brooks-lint/brooks-test/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.

agentmods 80×15 button for brooks-test

Your own site · 80×15
<a href="https://agentmods.dev/skills/hyhmrright/brooks-lint/brooks-test"><img src="https://agentmods.dev/badge/skills/hyhmrright/brooks-lint/brooks-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 161 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 389 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00161 $0.00389
Opus 5 $0.00081 $0.00195
Sonnet 5 $0.00032 $0.00078
Haiku 4.5 $0.00016 $0.00039

Measured 10d ago against content hash 8050877d3e0a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 10d 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.

skills/brooks-test/SKILL.md · 38 lines

What it actually says

Brooks-Lint — Test Quality Review

Setup

Read in order:

  1. ../_shared/common.md — Iron Law, Project Config, Report Template, Health Score
  2. ../_shared/source-coverage.md — book coverage, exceptions, tradeoffs
  3. ../_shared/test-decay-risks.md — test-space symptom definitions and sources
  4. test-guide.md (this directory) — the test quality review framework

Process

Scope: if the user did not share test files or point to a test directory, apply Auto Scope Detection (../_shared/common.md) first.

  1. Build the test suite map (guide's "Before You Start" section)
  2. Scan for each test decay risk in the order specified (Steps 1–4 of the guide)
  3. Apply the Iron Law and output using the Report Template (Step 5 of the guide)

Mode line in report: Test Quality Review

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 10d ago First seen · 38 lines · 161 tokens per session scan A 8050877d3e0a

Subscribe to this mod's changes

brooks-test is a skill published in the GitHub repository hyhmrright/brooks-lint (1,462 stars, last pushed 2d ago), licensed MIT. It adds 161 tokens to every session and 389 once invoked, about $0.0008 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.

Related

Other skills, from other repositories

write-tests

Write tests for existing production code. Processes ONE file at a time through a full pipeline: analyze, inventory (frozen BEFORE writing), write, executable coverage gate, verify, blind coverage audit, adversarial review, log. Uses CodeSift for discovery and analysis when available. Modes: [path] (specific target)…

greglas75/zuvo · 87 tokens

test-audit

Batch audit of test files against Q1-Q25 quality gates and AP1-AP32 anti-patterns. Detects orphan tests, phantom mocks, untested public methods. Tiered output (A/B/C/D) with critical gate enforcement and optional post-audit fix workflow. Flags: zuvo:test-audit all | [path] | [file] | --deep | --quick | --include-e2e |…

greglas75/zuvo · 100 tokens

test-implement

Implements React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks, setup, and browser harness. Use when creating or completing frontend tests and generated test skeletons.

shinpr/claude-code-workflows · 48 tokens

testing-laravel

Writes Laravel tests using PHPUnit. Use when "write tests", "add tests", "phpunit", "laravel test", "feature test", "unit test", "mock", "factory", or testing controllers, models, services, actions, jobs, artisan commands, or API endpoints.

iliaal/whetstone · 63 tokens

testing-react

Writes React/TypeScript tests using Vitest and React Testing Library. Use when "write react tests", "vitest", "component test", "hook test", "RTL", "testing library", "snapshot test", or testing React components, hooks, and utilities.

iliaal/whetstone · 57 tokens

mutation-test

Mutation testing with two engines. Uses the project's NATIVE mutation runner (StrykerJS / Infection / mutmut / PIT / cargo-mutants) when one is configured — installing it on explicit consent when it is not — for a reproducible, comparable score; and an LLM-guided engine for the mutation classes native mutators cannot…

greglas75/zuvo · 190 tokens