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 use-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/use-case-coverage)<a href="https://agentmods.dev/skills/ai-unified-process/marketplace/use-case-coverage"><img src="https://agentmods.dev/badge/skills/ai-unified-process/marketplace/use-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/use-case-coverage"><img src="https://agentmods.dev/badge/skills/ai-unified-process/marketplace/use-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.00232 | $0.02734 |
| Opus 5.5 | $0.00093 | $0.01094 |
| Sonnet 5.5 | $0.00046 | $0.00547 |
| Haiku 4.5 | $0.00023 | $0.00273 |
Grade A, and why
use-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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coverage Check (layered)
Instructions
Audit the use case $ARGUMENTS (UC-XXX) against the code
and tests that are supposed to realize it, and report the result.
This skill is the front door to the read-only uc-coverage-layered sub-agent of aiup-core. The audit
checklist — how coverage units are derived, which markers to search for, how each unit is judged —
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, so the two cannot drift apart. Your job is argument parsing, delegation, faithful
presentation of the report, 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 |
|---|---|
UC-001, UC001, uc 1, or a path to a specification |
the artifact to audit — normalize to UC-001, zero-padded to three digits |
TC-001, TC001 |
a journey — hand off to /test-case-coverage TC-XXX |
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 |
| two or more ids | a bounded sweep of exactly those ids |
| nothing | see Sweeps |
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 · 196 lines · 232 tokens per session scan A 5b050eb08270
use-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 232 tokens to every session and 2,734 once invoked, about $0.0009 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
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.