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 commands/leanandmean/mach10/test-auditgit clone --depth 1 https://github.com/LeanAndMean/mach10Wrote 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/leanandmean/mach10/test-audit)<a href="https://agentmods.dev/commands/leanandmean/mach10/test-audit"><img src="https://agentmods.dev/badge/commands/leanandmean/mach10/test-audit.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.00011 | $0.00894 |
| Opus 5 | $0.00005 | $0.00447 |
| Sonnet 5 | $0.00002 | $0.00179 |
| Haiku 4.5 | $0.00001 | $0.00089 |
Grade A, and why
test-audit 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Tests
You are performing a comprehensive audit of test quality across the repository (or a specified scope). The goal is to identify fake, meaningless, or low-quality tests — particularly those generated by AI that pass trivially without testing real behavior.
Context (optional): $ARGUMENTS
Step 1: Discover Tests
Find all test files in the repository (or specified scope):
- Python: Look for
test_*.py,*_test.py, files intests/directories - JavaScript/TypeScript: Look for
*.test.js,*.spec.ts, files in__tests__/directories - Other: Detect the project's test framework from config files (pytest.ini, jest.config.js, etc.)
If context was provided ($ARGUMENTS): if it looks like a file path or glob pattern, limit discovery to that directory or pattern; if it reads as prose, keep discovery repo-wide but note it as quality-focus guidance for Step 3 agents.
Step 2: Categorize
Group test files into logical categories by:
- Module or feature area they test
- Test type (unit, integration, e2e)
- Size (number of test cases)
Present the categories to the user as a summary table (category name, file count, test count).
Step 3: Fan Out Review Agents
For each category, delegate that category's test files to a general-purpose subagent for review. If prose context was provided in $ARGUMENTS, include it in each agent's prompt to steer the quality assessment (e.g., "focus on mocking patterns" or "prioritize the auth module"). Each agent should evaluate:
Quality criteria:
- Fake assertions: Tests that assert
True,is not Noneon values that can never be None, or other tautological checks - Mocked-everything tests: Tests where every dependency is mocked, so the test only verifies mock wiring rather than real behavior
- AI slop: Boilerplate tests that were clearly auto-generated and pass trivially (e.g., "test that function returns without error" with no meaningful assertion)
- Missing edge cases: Tests that only cover the happy path for functions with known edge cases
- Dead tests: Tests that are skipped, commented out, or unreachable
- Incorrect tests: Tests whose assertions don't actually verify the described behavior
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 · 77 lines · 11 tokens per session scan A c406ea6a2438
test-audit is a command published in the GitHub repository LeanAndMean/mach10 (20 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 894 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-30.
Other commands, from other repositories
culture-onboarding-90
Design a 90-day onboarding architecture for a role. First day (psychological safety + belonging activation), first week (relationship + role context + early wins), first month (skill ramp + integration + baseline), first quarter (autonomous performance + cultural integration check). Written-first elements for…
perf-difficult-conversation
Three-conversations framework rehearsal (Stone/Patton/Heen — Harvard Negotiation Project) for high-stakes conversations — termination, demotion, hard feedback, conflict surfacing. Produces three-conversations breakdown (what-happened / feelings / identity), conversation script with multiple opening choices, SCARF…
design-regimen
Design an integrated weekly regimen — training, nutrition, sleep, stress, recovery — matched to the person's actual life. Composes with gym-training-expert and health-nutrition-expert for domain detail. Produces a sustainable architecture, not an extreme program. Not medical advice.
hire-calibrate
Run the pre-loop calibration session — 60 minutes with ≥3 raters, review the rubric, score 2 anchor candidates the team has previously seen, surface inter-rater drift, agree on hire-bar examples. The calibration session itself is the deliverable. Without it, the loop runs on uncalibrated rulers. Per Project Oxygen …
reclaim-knowledge
Organize scattered professional material into a domain-based second-brain architecture. Maps existing sources (Canva, Drive, local folders, Notion, screenshots) to functional domains. Non-technical-friendly — produces folder structure + drag-and-drop instructions, not CLI commands.
build-brand-kit
Produce a complete Brand Kit — positioning, voice rules, color palette, typography stack, visual vocabulary, example applications, don'ts — derived from the person's Genius Profile and Vision Architecture. Composes with frankx-brand, brand-voice, brand-guidelines, theme-factory, infogenius. Integrates with…