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 coverage-checkgit 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/coverage-check)<a href="https://agentmods.dev/skills/ai-unified-process/marketplace/coverage-check"><img src="https://agentmods.dev/badge/skills/ai-unified-process/marketplace/coverage-check/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/coverage-check"><img src="https://agentmods.dev/badge/skills/ai-unified-process/marketplace/coverage-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 157 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00218 | $0.02143 |
| Opus 5 | $0.00109 | $0.01071 |
| Sonnet 5 | $0.00044 | $0.00429 |
| Haiku 4.5 | $0.00022 | $0.00214 |
Grade A, and why
coverage-check 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 10d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coverage Check
Instructions
Audit the artifact $ARGUMENTS — a use case (UC-XXX) or a test case (TC-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 sub-agent of this plugin. The audit
checklist — how coverage units are derived, which markers to search for, how each unit is judged —
lives in agents/uc-coverage.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 |
audit a test case journey instead |
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.
- 10d ago First seen · 159 lines · 218 tokens per session scan A 976f31533a1a
coverage-check is a skill published in the GitHub repository AI-Unified-Process/marketplace (123 stars, last pushed 11d ago), licensed Apache-2.0. It adds 218 tokens to every session and 2,143 once invoked, about $0.0011 per session on Opus 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-08-30.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.