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 fabioc-aloha/Alex_Skill_Mall --skill autocoveragegit clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_MallWrote 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/fabioc-aloha/alex_skill_mall/autocoverage)<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/autocoverage"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/autocoverage/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/fabioc-aloha/alex_skill_mall/autocoverage"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/autocoverage.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.00083 | $0.14831 |
| Opus 5 | $0.00042 | $0.07415 |
| Sonnet 5 | $0.00017 | $0.02966 |
| Haiku 4.5 | $0.00008 | $0.01483 |
Grade C, and why
autocoverage scanned grade C with 1 finding 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 8d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
1. **Clean and build locally** (ALL languages): clean stale build artifacts before building (`dotnet clean`, `cargo clean`, `rm -rf dist/`, `npm run clean`, etc.) to prevent inflated coverage from outdated binaries. Then How it starts
The opening of the file, as written. The whole thing — 938 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto Unit Test Generator
Constraints (apply at ALL stages)
DO:
- Run until target coverage is reached or all modules are terminal (done/stalled)
- Use measured coverage gaps as input -- never guess
- Prioritize exception handlers, error paths, retry logic, validation
- Build and pass all tests locally before every commit
- Prove a measured coverage delta each iteration
- Branch from default integration branch; atomic commits per iteration
- Stick to verified facts from repo files, commands, and recorded artifacts -- never assume
NEVER:
- Generate tests on a broken build
- Test constants, DTOs, constructors, properties, default values, or logging
- Create a test project in the same folder as an existing project
- Rename folders, move files, rename projects, or change production code
Skill structure
SKILL.md -- Pipeline (this file)
scripts/
parse-cobertura.ps1 -- Parse Cobertura XML into JSON
parse-coverage-text.ps1 -- Parse pytest/Jest/Vitest text coverage into JSON
references/
code-coverage.md -- Coverage commands, tools, parsing
test-planning.md -- Prioritization + plan format
test-generation.md -- Code gen rules, framework compat, Moq, metadata
test-quality.md -- Anti-patterns, review checklist, quality gate
test-finalization.md -- Incorporate feedback, produce final code
ci-pipeline-checklist.md -- PR/pipeline readiness
skill-templates.md -- Reusable output templates
pr-description-template.md -- Final PR description template
Reference Lookup
Load the reference file(s) when entering the listed stage.
| Stage | Reference file(s) |
|---|---|
| 2, 7 | code-coverage.md |
| 3 | test-planning.md |
| 4 | test-generation.md, test-quality.md |
| 5 | test-quality.md, test-finalization.md |
| 7 (PR) | pr-description-template.md |
| Pre-PR | test-quality.md, test-finalization.md |
| CI | ci-pipeline-checklist.md |
| any | skill-templates.md |
What ships with it
11 files 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.
- references/ci-pipeline-checklist.md 5.0 KB
- references/code-coverage.md 4.5 KB
- references/gotchas.md 4.8 KB
- references/pr-description-template.md 7.2 KB
- references/skill-templates.md 8.7 KB
- references/test-finalization.md 8.2 KB
- references/test-generation.md 13 KB
- references/test-planning.md 5.6 KB
- references/test-quality.md 12 KB
- scripts/parse-cobertura.ps1 9.7 KB runs code
- scripts/parse-coverage-text.ps1 7.7 KB runs code
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.
- 8d ago First seen · 938 lines · 83 tokens per session scan C 7734970d27e2
autocoverage is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 14,831 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
flutter-bloc-state-management
Implement BLoC/Cubit state, events, transitions, and async concurrency in Flutter. Use for BLoC/Cubit feature logic, debounced/cancellable events, state rendering, or bloc tests—not generic widget-only work.
unit-test
A Go testing workflow for writing unit tests: small tests that check individual functions or components. It supports table-driven cases, where many inputs and expected results are organised in one test, and subtests.
fuzzing-test
A Go testing guide for generating fuzz tests, which repeatedly try varied inputs to find crashes and unexpected behavior. It first checks whether the code is suitable for fuzzing.
test-component
Write React Testing Library tests for an existing component, following the project's RTL conventions (prefer role/label queries, mock at network boundary, no act()). Invoke when the user asks to test, add tests for, or cover a component.
adept-writing-tests
How to write tests in the adept Go codebase — table-driven tests with testify, golden fixtures under testdata/, the cmd/adept e2e harness, temp-dir/HOME isolation, and coverage gates. Apply when adding or changing Go tests here. (matches: /test.go).
qt-qml-test-run
Builds and runs Qt Quick Test (qmltestrunner / CTest) for a QML project, then writes a Markdown report. Use for "run qml tests", "run qmltestrunner".