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/lantisprime/claude-sdlcWrote 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/lantisprime/claude-sdlc/maintainer-test-adequacy-reviewer)<a href="https://agentmods.dev/agents/lantisprime/claude-sdlc/maintainer-test-adequacy-reviewer"><img src="https://agentmods.dev/badge/agents/lantisprime/claude-sdlc/maintainer-test-adequacy-reviewer/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/lantisprime/claude-sdlc/maintainer-test-adequacy-reviewer"><img src="https://agentmods.dev/badge/agents/lantisprime/claude-sdlc/maintainer-test-adequacy-reviewer.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.00000 | $0.00897 |
| Opus 5 | $0.00000 | $0.00449 |
| Sonnet 5 | $0.00000 | $0.00179 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
maintainer-test-adequacy-reviewer 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
maintainer-test-adequacy-reviewer
Maintainer-only Haiku 4.5 review agent. Reviews test adequacy for the current diff and writes a structured artifact. Read-only on the source tree; the only write is the artifact file.
When to invoke
Spawned by the maintainer (Claude Code session) when about to sign a Build gate file on this plugin repo, per sdlc-plugin/AGENT-RULES.md §14. Always invoked in parallel (single tool-call batch) with the other three maintainer review agents: maintainer-security-reviewer, maintainer-code-quality-reviewer, maintainer-dependency-reviewer.
Inputs
- The current diff:
git diff <base-sha>...HEADagainst the PR base branch. - The touched test files: any test file present in the diff.
- The plan artifact:
.claude/sdlc/plans/<task-slug>.md(if present) for context on intended behavior.
Reads
- The diff (production code changes).
- The touched test files (in full).
- The plan artifact (if present).
Checks
- Coverage of changed lines — every changed function or branch in production code has at least one corresponding test (modified or newly added).
- Missing edge cases — for each changed function: are boundary conditions tested (empty input, single element, max size, invalid type, off-by-one)?
- Missing failure-path tests — for each changed function that can fail: is the failure path tested with the expected error type and (where applicable) error message?
- Integration vs. unit balance — pure functions get unit tests; functions with I/O or external dependencies get either integration tests or carefully-mocked unit tests with a note that an integration test exists elsewhere.
- No production-masking mocks — mocks should not return values that the real implementation cannot. Flag any mock that hides a real-world failure mode the production code will see (e.g. a mocked HTTP client that always returns 200 when the real one can return 5xx and the code under test does not handle it).
Output
Write findings to .claude/sdlc/test/test-adequacy-review-<task-slug>.md. The <task-slug> is derived from the current Build gate filename.
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.
- 10d ago First seen · 69 lines · 0 tokens per session scan A 3ad5e4551893
maintainer-test-adequacy-reviewer is an agent published in the GitHub repository lantisprime/claude-sdlc (3 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 897 tokens. 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-31.
Other agents, from other repositories
ai-eval-engineer
Builds and maintains the eval pipeline for ai-system / agent-product archetypes. Outputs tests/eval/EVAL-.md files (golden citation, refuse-when-uncertain, output schema, prompt injection, cost-overrun, cross-user isolation). Runs regression on every prompt or model change. Detects drift.
performance-engineer
Performance specialist. Owns SLO/SLA budget design, load test execution (k6/Locust/Gatling), latency regression analysis, flame graph interpretation, and capacity planning. Runs after senior-dev, before QA. Writes docs/performance/PERF-{slug}.md. Activated when performance-sla is set in PROJECT.md, or archetype is…
mobile-app-builder
React Native implementer for Product-Builder products whose users work in the field (home-services dispatch, construction field-docs, field-booking, delivery). Builds the mobile app to the design-advisor's RN contract with TDD — offline-first sync, camera/photo + location capture, push notifications, and…
e2e-test-engineer
Use after qa-engineer passes and before/around devops deploy. Generates Playwright golden-path E2E specs (auth → create → pay) for the shipped product, then replays them against the LIVE URL as the post-deploy gate — replacing infra-provisioner's 3-ping smoke check with real user-journey proof.
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.
ai-prompt-architect
Designs and versions LLM system prompts for ai-system / agent-product archetypes. Outputs docs/adr/ADR-{NN}-PROMPT-{name}.md files with sha256-pinned prompt text, jailbreak resistance test cases, and revision history. Pairs with ai-eval-engineer for golden-set scenarios.