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 skills add thermiteau/maverick --skill mav-bp-testinggit clone --depth 1 https://github.com/thermiteau/maverickWrote 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/skills/thermiteau/maverick/mav-bp-testing)<a href="https://agentmods.dev/skills/thermiteau/maverick/mav-bp-testing"><img src="https://agentmods.dev/badge/skills/thermiteau/maverick/mav-bp-testing/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/skills/thermiteau/maverick/mav-bp-testing"><img src="https://agentmods.dev/badge/skills/thermiteau/maverick/mav-bp-testing.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.00061 | $0.00851 |
| Opus 5 | $0.00030 | $0.00426 |
| Sonnet 5 | $0.00012 | $0.00170 |
| Haiku 4.5 | $0.00006 | $0.00085 |
Grade A, and why
mav-bp-testing 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 9d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Standards
Unit and integration testing as one discipline. Unit tests verify behaviour in isolation; integration tests verify real wiring across boundaries. Together they are the only automated evidence that generated code actually works.
Maverick's Rules
Unit tests
- Test behaviour, not implementation. Assert on outputs and effects, never on reimplemented logic (tautological tests) or internal calls.
- Mock at the boundary only (APIs, DB, filesystem). Never mock what you own; prefer stubs over mocks; >3 mocks in one test means the unit's design is wrong.
- No logic in tests — no conditionals, loops, or try/catch in test bodies. No test interdependence. Delete flaky tests rather than keep them.
- A unit test taking >100ms is hitting real I/O — fix it.
Integration tests
- Complement, don't duplicate — cover cross-boundary behaviour (endpoints, persistence, external clients); never re-test unit-covered logic.
- Each test owns its data and cleans up; parallel runs never collide.
- Real dependencies in order of preference: containers → sandboxes → fakes. Never production services.
- Health-check polling with timeouts, never sleeps. Every test has an explicit timeout.
Coverage (enforced, not aspirational)
- Unit: 60% minimum, gated in CI — the build fails below it. The number is a floor, not a goal: coverage with weak assertions is worse than less coverage with strong ones.
- Integration: every critical cross-boundary path (auth, payment, persistence, external APIs) has at least one test, and coverage must not decrease — a ratchet, not a percentage floor.
Project Implementation Lookup
Check docs/maverick/skills/unit-testing/SKILL.md and
docs/maverick/skills/integration-testing/SKILL.md for the project's
framework, conventions, and extra requirements. If present, they win on
specifics. If missing, proceed with these standards and note the gap in
your summary — do not trigger skill generation mid-task.
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.
- 9d ago First seen · 75 lines · 61 tokens per session scan A 8361f26cbbf7
mav-bp-testing is a skill published in the GitHub repository thermiteau/maverick (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 851 once invoked, about $0.0003 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 skills, from other repositories
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
testing-llm
LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.