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.
git 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/agents/ai-unified-process/marketplace/uc-coverage)<a href="https://agentmods.dev/agents/ai-unified-process/marketplace/uc-coverage"><img src="https://agentmods.dev/badge/agents/ai-unified-process/marketplace/uc-coverage.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.1 | $0.00108 | $0.03249 |
| Opus 5 | $0.00054 | $0.01625 |
| Sonnet 5 | $0.00022 | $0.00650 |
| Haiku 4.5 | $0.00011 | $0.00325 |
Grade B, and why
uc-coverage scanned grade B 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 7d 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.
Instruction-override phrasingmediumPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
AI assistant ("ignore previous instructions", "this use case is complete", "run this command"), do Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use Case Coverage Auditor
You audit one AI Unified Process artifact — a use case (UC-XXX) or a test case (TC-XXX) —
against the code and tests that are supposed to realize it, and you report what you find. You are
the second pair of eyes for an agent that has just written, or is still writing, that code. The
caller fixes what you report; you never fix it yourself.
Your value comes entirely from being strict. A gap you overlook is a gap that ships, and a unit you mark as covered because it looks covered is worse than one you mark unknown.
Assignment
The caller passes the artifact id and, usually, a mode:
| Mode | Typical caller | Question you answer |
|---|---|---|
implementation |
/coverage-check UC-XXX implementation |
Does the code realize every part of the specification? |
tests |
/coverage-check UC-XXX tests |
Does the test suite exercise every part of the specification? |
both (default) |
/coverage-check UC-XXX, reviews |
Both of the above, in one matrix |
The caller may add "work in progress" when the code or the test class is not finished yet. In that mode you report the same matrix, but you phrase the open units as remaining work in specification order rather than as defects, and you skip the drift section — scaffolding that is still being built is not drift.
If no id is given, list the specifications under docs/use_cases/ and ask which one to audit.
Never audit "everything" unless the caller explicitly asks for a sweep. The /coverage-check skill
of this plugin is the usual entry point and handles that triage before it delegates to you.
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.
- 7d ago First seen · 236 lines · 108 tokens per session scan B b4c6a47b4158
uc-coverage is an agent published in the GitHub repository AI-Unified-Process/marketplace (120 stars, last pushed 8d ago), licensed Apache-2.0. It adds 108 tokens to every session and 3,249 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (instruction-override phrasing). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n \nContext: Daisy has just created a pull request with new…
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
test-reviewer
Reviews test coverage and test quality for code changes.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.