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 irahardianto/awesome-agv --skill test-unitgit clone --depth 1 https://github.com/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/test-unit)<a href="https://agentmods.dev/skills/irahardianto/awesome-agv/test-unit"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/test-unit/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/irahardianto/awesome-agv/test-unit"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/test-unit.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.00041 | $0.01009 |
| Opus 5.5 | $0.00016 | $0.00404 |
| Sonnet 5.5 | $0.00008 | $0.00202 |
| Haiku 4.5 | $0.00004 | $0.00101 |
Grade A, and why
test-unit 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Improve Unit Test Coverage
Entry-point guard: This is a user-invoked command skill (
/test-unit). If you are a spawned subagent, do NOT execute this skill — return to your assigned scope card.
Purpose
Retroactive unit test coverage improvement for existing codebases. For greenfield development, use /workflow-solo — TDD is built in.
When to Use
- Existing codebase with insufficient unit test coverage
- Post-mortem finding: "we need more tests"
- Pre-release hardening
- Quality improvement initiative
When NOT to Use
- Greenfield development (use
/workflow-solo— TDD is built in) - Integration test gaps (use
/test-integrationskill) - E2E test gaps (use
/test-e2eskill) - Need test scenarios first (use
/test-scenariosskill)
Phases
Phase 1: ANALYZE
Objective: Map current coverage gaps.
- Load applicable idiom skill(s) — each defines the coverage tool (e.g., Go:
go test -coverprofile, TS:vitest --coverage, Python:pytest-cov) - Run coverage tool against the full codebase
- Parse coverage report — identify files and functions with lowest coverage
- Produce Coverage Gap Map artifact with: file path, current coverage %, lines uncovered, module/feature area. Sort by coverage ascending.
Gate: Coverage gap map artifact created with baseline metrics.
Phase 2: PRIORITIZE
Objective: Rank gaps by business impact for user review.
Prioritization criteria (highest → lowest):
- Critical business logic — payment, auth, core domain rules
- High-churn files — use
git log --format='%H' --follow <file> | wc -lto find frequently changed files - Public API surface — exported functions/methods used by other modules
- Error handling paths — catch/error blocks with no test coverage
- Utilities and helpers — lowest priority unless widely imported
Steps:
- Cross-reference coverage gaps with git churn data
- Categorize each gap by criteria above
- Present prioritized list to user for confirmation
- User selects which gaps to address in this iteration
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 · 103 lines · 41 tokens per session scan A 705534ce3077
test-unit is a skill published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 1,009 once invoked, about $0.0002 per session on Opus 5.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-10-15.
Other skills, from other repositories
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
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.
angular-testing
Write Angular component tests using TestBed, ComponentHarness, and HttpTestingController with proper signal input handling. Use when writing component tests, mocking HTTP calls, or testing signal inputs.
mlops-validation
Add the validation layers that gate a merge — ty typing, Ruff linting, pytest coverage, structured logging, and the trivy, pip-audit, and gitleaks scans. Use when hardening code quality or wiring the mise run check task.
testing
Testing strategies and methodologies including TDD and E2E testing. Use when writing tests, implementing TDD workflow, or setting up E2E test infrastructure.
testing-guide
A testing guide covering the test pyramid and standards for unit, integration, system, and end-to-end tests.