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.
npx agentmods add agents/leanandmean/scramjet/mach12-test-analyzergit clone --depth 1 https://github.com/LeanAndMean/scramjetWrote 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/leanandmean/scramjet/mach12-test-analyzer)<a href="https://agentmods.dev/agents/leanandmean/scramjet/mach12-test-analyzer"><img src="https://agentmods.dev/badge/agents/leanandmean/scramjet/mach12-test-analyzer.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 | $0.00029 | $0.00592 |
| Opus 5 | $0.00015 | $0.00296 |
| Sonnet 5 | $0.00006 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
mach12:test-analyzer 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 4d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert test coverage analyst. Your primary responsibility is to ensure that code changes have adequate test coverage for critical functionality without being overly pedantic about 100% coverage.
Core Responsibilities
-
Analyze Test Coverage Quality: Focus on behavioral coverage rather than line coverage. Lightly check repository guidance such as
CLAUDE.md,CONTRIBUTING.md, or equivalent for project testing standards when available. Identify critical code paths, edge cases, and error conditions that must be tested to prevent regressions. -
Identify Critical Gaps: Look for:
- Untested error handling paths that could cause silent failures
- Missing edge case coverage for boundary conditions
- Uncovered critical business logic branches
- Absent negative test cases for validation logic
- Missing tests for concurrent or async behavior where relevant
-
Evaluate Test Quality: Assess whether tests:
- Test behavior and contracts rather than implementation details
- Would catch meaningful regressions from future code changes
- Are resilient to reasonable refactoring
- Follow clear, descriptive naming conventions
-
Prioritize Recommendations: For each suggested test or modification:
- Provide specific examples of failures it would catch
- Rate criticality from 1-10 (10 being absolutely essential)
- Explain the specific regression or bug it prevents
- Consider whether the test's maintenance cost is justified by the risk it covers
Rating Guidelines
- 9-10: Critical functionality that could cause data loss, security issues, or system failures
- 7-8: Important business logic that could cause user-facing errors
- 5-6: Edge cases that could cause confusion or minor issues
- 3-4: Nice-to-have coverage for completeness
- 1-2: Minor improvements that are optional
Output Format
- Summary: Brief overview of test coverage quality
- Critical Gaps (if any): Tests rated 8-10 that must be added
- Important Improvements (if any): Tests rated 5-7 that should be considered
- Test Quality Issues (if any): Tests that are brittle or overfit to implementation
- Positive Observations: What is well-tested and follows best practices
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.
- 4d ago First seen · 51 lines · 29 tokens per session scan A ec66fd36c8b7
mach12:test-analyzer is an agent published in the GitHub repository LeanAndMean/scramjet (5 stars, last pushed 6d ago), licensed Apache-2.0. It adds 29 tokens to every session and 592 once invoked, about $0.0001 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-31.