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 jaktestowac/awesome-copilot-for-testers --skill requirements-test-coverage-mappergit clone --depth 1 https://github.com/jaktestowac/awesome-copilot-for-testersWrote 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/jaktestowac/awesome-copilot-for-testers/requirements-test-coverage-mapper)<a href="https://agentmods.dev/skills/jaktestowac/awesome-copilot-for-testers/requirements-test-coverage-mapper"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/requirements-test-coverage-mapper/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/jaktestowac/awesome-copilot-for-testers/requirements-test-coverage-mapper"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/requirements-test-coverage-mapper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00110 | $0.01586 |
| Opus 5 | $0.00055 | $0.00793 |
| Sonnet 5 | $0.00022 | $0.00317 |
| Haiku 4.5 | $0.00011 | $0.00159 |
Grade A, and why
requirements-test-coverage-mapper 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements → Test Coverage Mapper (RTM)
This skill turns a PRD, user stories, acceptance criteria, and constraints into a traceability-driven test coverage plan:
- a Requirements Traceability Matrix (RTM)
- a gap & ambiguity report
- test design recommendations across levels (unit/API/UI/e2e/non-functional)
- automation candidates and CI gating suggestions
The output is designed to be used as a living artifact and single source of truth for coverage, readiness, and auditability.
When to Use
Use this skill when you need to:
- Validate coverage completeness before/after implementation
- Convert PRD/user stories into a test plan that is traceable and reviewable
- Identify missing acceptance criteria, ambiguous requirements, or hidden scope
- Support change impact analysis when requirements evolve
- Build a risk-based regression strategy or release readiness assessment
Operational Workflow
Phase 0: Strategy Selection (Context First)
Classify the work to adjust rigor and output depth:
- Delivery stage: MVP / Iteration / Hardening / Release / Hotfix
- Domain risk: Low / Medium / High (payments, auth, compliance = high)
- Change surface: UI / API / Data / Infra / Cross-cutting
- AI criticality: None / Supporting / Core
- Target tooling (optional): Jira / Azure DevOps / TestRail / GitHub Issues
If unknown, mark as TBD and proceed with safe defaults.
Phase 1: Discovery
Ask targeted questions where the answer would change the coverage plan. Cover these areas:
- Test basis source - PRD link/text? user stories? AC? designs? (what is the "source of truth"?)
- Scope boundaries - what is explicitly in/out? any non-goals?
- Quality attributes - performance, security, accessibility, reliability, observability expectations?
- Data & environments - test envs available, data seeding/masking rules, third-party dependencies?
- Release constraints - deadline, MVP cuts, rollout type (flagged, staged, big-bang)?
- Definition of Done / acceptance - who signs off and what evidence is required?
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 144 lines · 110 tokens per session scan A 07a05b1ccc33
requirements-test-coverage-mapper is a skill published in the GitHub repository jaktestowac/awesome-copilot-for-testers (113 stars, last pushed 14d ago), licensed MIT. It adds 110 tokens to every session and 1,586 once invoked, about $0.0006 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
fix-tests
Focus on all unit + command tests (pytest --exclude tests/integration). Make sure they pass and fix errors. If you run into anything very odd: stop, and let me know. Mutate test code first and let me know if you think you should update application code.
character-animation-qa
Review local character animation with schema checks, Playwright browser previews, frame sampling, and FFmpeg/ffprobe final output checks.
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
crap-score
Calculates CRAP (Change Risk Anti-Patterns) for a named .NET method, class, or file. USE FOR: explicit CRAP calculation or coverage-and-complexity risk within that named target, including which tests to prioritize. DO NOT USE FOR: project-wide coverage/CRAP, plateaus, or project-wide blockers/priorities…
nunit
Write, run, or repair .NET tests that use NUnit. Use when a repo uses NUnit, [Test], [TestCase], [TestFixture], or NUnit3TestAdapter for VSTest or Microsoft.Testing.Platform execution. USE FOR: writing or reviewing NUnit tests; using [Test], [TestCase], [TestFixture], [SetUp], [TearDown] attributes; configuring…
michel-create-packmind-dataset
Seed a local Packmind instance with a realistic dataset — one organization populated with standards, commands, and skills — so an autonomous agent can exercise its own changes against lifelike data instead of an empty app. Use this whenever you need populated Packmind data to verify a change end-to-end: reproducing a…