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 skills/ivy00johns/skill-madness/coverage-loopnpx skills add ivy00johns/Skill-Madness --skill coverage-loopgit clone --depth 1 https://github.com/ivy00johns/Skill-MadnessWrote 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/ivy00johns/skill-madness/coverage-loop)<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/coverage-loop"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/coverage-loop.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.00194 | $0.02805 |
| Opus 5 | $0.00097 | $0.01403 |
| Sonnet 5 | $0.00039 | $0.00561 |
| Haiku 4.5 | $0.00019 | $0.00281 |
Grade A, and why
coverage-loop 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 3d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
coverage-loop
A configuration of [
loop-controller]. That skill supplies the loop machinery — primitive selection, the full guardrail stack, state externalization. This skill supplies the two things specific to "grow the suite to a coverage number": a mechanical proof (the coverage report meets the configured target with a green suite) and the anti-gaming discipline that keeps the number honest. Readloop-controllerfor the guardrails; they're inherited, not repeated here.Why
disable-model-invocation: this loop writes test files and commits on its own and spends tokens re-running the full coverage suite each round, until the target is hit. You want to type/coverage-loop(or have the orchestrator dispatch it) — not have Claude start an autonomous test-writing loop because some file looked under-tested.
The 5-part contract
| Part | This loop |
|---|---|
| trigger | coverage below the configured target, a build wave needing more tests, or an explicit /coverage-loop (optionally scoped to a path or per-target) |
| action | ONE iteration: run coverage → find the lowest-covered meaningful unit → add real, behavior-checking tests for it → re-run coverage over the whole report (and the full suite) |
| proof | the coverage report shows total AND every configured per-target threshold >= the target AND the full suite exits 0 — default-FAIL: assume below target until the freshly-generated report proves otherwise, read from the named artifact (coverage.xml / lcov.info / the N% covered summary line), not from memory of a prior run |
| memory | coverage_plan.md (the live TODO of under-covered units + a per-round unit → tests added → new % log), plus a git checkpoint per coverage-raising round |
| stop | report meets target with the suite green OR iteration cap OR no-progress for 3 rounds OR budget cap |
The proof: a fresh coverage report at-or-above target, default-FAIL
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 195 lines · 194 tokens per session scan A 73810ecd0296
coverage-loop is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed 23d ago), licensed MIT. It adds 194 tokens to every session and 2,805 once invoked, about $0.0010 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
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
agui-dotnet-unit-tests
Author unit tests for the AG-UI .NET SDK (the .UnitTests projects), following the SDK's serialization and compatibility conventions. USE FOR: adding unit-test coverage for a new type/method in AGUI.Abstractions/Formatting/Protobuf/Client/Server, event serialization round-trips, JsonDocument property-name assertions…
prowler-test-api
Testing patterns for Prowler API: JSON:API, Celery tasks, RLS isolation, RBAC. Trigger: When writing tests for api/ (JSON:API requests/assertions, cross-tenant isolation, RBAC, Celery tasks, viewsets/serializers).
gen-test
Generate idiomatic tests for Go packages and handlers in the Meshery project.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
nunit-testing
Use when writing or modifying tests in NUnit's own test projects, or when making a behavioral change to production code that needs test coverage. Covers test structure, attribute choice, helper visibility, platform guards, and which test projects are real.