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 AI-Unified-Process/marketplace --skill test-case-coveragegit clone --depth 1 https://github.com/AI-Unified-Process/marketplaceWrote 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/ai-unified-process/marketplace/test-case-coverage)<a href="https://agentmods.dev/skills/ai-unified-process/marketplace/test-case-coverage"><img src="https://agentmods.dev/badge/skills/ai-unified-process/marketplace/test-case-coverage/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/ai-unified-process/marketplace/test-case-coverage"><img src="https://agentmods.dev/badge/skills/ai-unified-process/marketplace/test-case-coverage.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.00239 | $0.01438 |
| Opus 5.5 | $0.00096 | $0.00575 |
| Sonnet 5.5 | $0.00048 | $0.00288 |
| Haiku 4.5 | $0.00024 | $0.00144 |
Grade A, and why
test-case-coverage 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 today.
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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coverage Check (test case)
Instructions
Audit the test case $ARGUMENTS against the journey test and the code that are supposed to realize it, and report the result.
This skill is a front door to the read-only uc-coverage-layered sub-agent of aiup-core, the same agent
/use-case-coverage uses. The audit checklist lives in agents/uc-coverage-layered.md at the plugin root (locate
it with a glob for **/agents/uc-coverage-layered.md) and is deliberately not repeated here. How a report is
presented, compared with an earlier run, and run on a host without sub-agents is owned by /use-case-coverage:
locate it with a glob for **/*use-case-coverage/SKILL.md (the folder may carry a host prefix such as
tessl__use-case-coverage) and apply its sections "Delegation", "Repeated Runs", and "Hosts without sub-agents" as
written. Your job is argument parsing, delegation, faithful presentation, and offering the next step.
The report is the deliverable. You do not fix what it finds.
Arguments
Everything is parsed out of $ARGUMENTS; the tokens may appear in any order.
| Token | Meaning |
|---|---|
TC-001, TC001, tc 1, or a path to a test case |
the journey to audit — normalize to TC-001 |
implementation, impl, code |
mode implementation |
tests, test |
mode tests |
both, or no mode token at all |
mode both (the default) |
wip, --wip, work in progress, in progress, draft |
pass the work-in-progress qualifier through |
a UC-* id |
not a journey — hand off to /use-case-coverage UC-XXX |
| nothing | list the test cases and ask — see below |
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.
- today First seen · 96 lines · 239 tokens per session scan A 9c96e520d825
test-case-coverage is a skill published in the GitHub repository AI-Unified-Process/marketplace (150 stars, last pushed yesterday), licensed Apache-2.0. It adds 239 tokens to every session and 1,438 once invoked, about $0.0010 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-25.
Other skills, from other repositories
test-conversion-reviewer
Reviewer for converting unit tests to browser tests for Project Bedrock. Invoke this when the user needs to review their work while removing complex Browser dependencies from tests.
ln-51-acceptance-test-builder
Builds, updates or retires scoped acceptance tests and verifies execution; does not repair product code.
playwright-e2e-review
Audit Playwright E2E tests in the gc.platform suite (tests/playwright) against the four hard rules — no mocks, Page Object Model, work-by-fixture, one folder per frontend feature module — plus strict-TypeScript quality. Use whenever the user wants to review, check, audit, or "make sure it follows the conventions" for…
full-stack-e2e-review
Run a rigorous end-to-end product or feature review across architecture, data, APIs, permissions, billing, tests, and real browser UX. Use for requests such as review this branch end to end, test everything, ensure no bugs, perform a full visual pass, or validate a multi-user workflow before merge or deploy.
triaging-visual-review-runs
Inspects PostHog Visual Review (VR) runs that gate PR merges with screenshot regression checks. Use when the user mentions "visual review", "VR", "snapshot diff", "screenshot test", "storybook regression", "playwright snapshot", "quarantine", asks why a PR is blocked or what changed visually, wants to triage the VR…
merge-ready
Run all quality gates before merge — git hygiene, documentation completeness, code review, security audit, build, E2E, goal-backward verification, doc accuracy and UI/UX — then write the changelog entry.