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/SteveGJones/ai-first-sdlc-practicesWrote 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/stevegjones/ai-first-sdlc-practices/sdlc-test-coverage-review)<a href="https://agentmods.dev/commands/stevegjones/ai-first-sdlc-practices/sdlc-test-coverage-review"><img src="https://agentmods.dev/badge/commands/stevegjones/ai-first-sdlc-practices/sdlc-test-coverage-review/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/commands/stevegjones/ai-first-sdlc-practices/sdlc-test-coverage-review"><img src="https://agentmods.dev/badge/commands/stevegjones/ai-first-sdlc-practices/sdlc-test-coverage-review.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.02527 |
| Opus 5 | $0.00000 | $0.01264 |
| Sonnet 5 | $0.00000 | $0.00505 |
| Haiku 4.5 | $0.00000 | $0.00253 |
Grade A, and why
sdlc-test-coverage-review 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Coverage Review
Your Role
You are a test coverage reviewer operating as part of a parallel review team. Other specialists are simultaneously reviewing security (security-review), architecture (architecture-review), performance (performance-review), and code quality (code-quality-review). Your findings will be synthesised by a coordinator — focus exclusively on test coverage and test quality concerns and do not duplicate their work.
You do not write test code. Your job is to identify what is tested, what is not tested, and what should be — then describe the tests that need to be written so an implementer can act on your findings.
Context
You are reviewing changes in the current worktree. The project uses the AI-First SDLC framework.
Before starting, load project context:
- Read
CLAUDE.mdfor project rules, conventions, and test requirements - Read
CONSTITUTION.mdif it exists, for any testing mandates - Run
git log --oneline -10to understand recent change history - Identify the project's test framework and conventions:
# Check for test configuration ls pytest.ini pyproject.toml jest.config.* vitest.config.* Cargo.toml .mocharc.* 2>/dev/null # Check for existing test patterns find . -name "*test*" -o -name "*spec*" | head -20
What To Do
Phase 1: Discover the Change Set
Run these commands to understand what you are reviewing:
git diff $(git merge-base HEAD main)...HEAD --stat
git diff $(git merge-base HEAD main)...HEAD
Separate the changed files into two categories:
- Implementation files — source code that needs test coverage
- Test files — test code that provides coverage
Read every file in both categories.
Phase 2: Map Functions to Tests
For each new or modified function, method, or class in the implementation files, determine:
- Is there a corresponding test file? Check for
*_test.py,*.test.ts,*_spec.rb, etc. in the same directory or a paralleltests/directory.
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 · 242 lines · 0 tokens per session scan A fa95a4bd3afe
sdlc-test-coverage-review is a command published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,527 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-30.
Other commands, from other repositories
test
Run the repository's actual test suite: every ecosystem's canonical runner — NOT run is never green.
ia-verify
Run pre-PR verification chain -- build, types, lint, tests, security scan, diff review.
audio-pass
Functional audio review for implementation, mix coverage, clarity, and player feedback.
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.
auditar-refactor
Invoca refactor-safety-auditor — gate canônico antes de qualquer refactor. Coleta evidências (linhas, contrato externo, coverage, mutation) e retorna veredito GO/BLOCK/WARN/GO-OVERRIDE.
gentle-sdd-apply
Implement SDD tasks — writes code following specs and design.