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 ArabelaTso/Skills-4-SE --skill requirement-coverage-checkergit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote 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/arabelatso/skills-4-se/requirement-coverage-checker)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/requirement-coverage-checker"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/requirement-coverage-checker/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/arabelatso/skills-4-se/requirement-coverage-checker"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/requirement-coverage-checker.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.00071 | $0.00637 |
| Opus 5 | $0.00036 | $0.00318 |
| Sonnet 5 | $0.00014 | $0.00127 |
| Haiku 4.5 | $0.00007 | $0.00064 |
Grade A, and why
requirement-coverage-checker 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 9d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirement Coverage Checker
Systematically verify that design and implementation cover all specified requirements. Identifies gaps, ensures traceability, and validates that every requirement has corresponding design elements, code, and tests.
Core Capabilities
1. Requirement Extraction
Parse and identify requirements from documents:
- Functional requirements - Feature specifications
- Non-functional requirements - Performance, security, usability
- Business rules - Constraints and policies
- User stories - As-a/I-want/So-that format
- Use cases - Actor-goal scenarios
- Acceptance criteria - Success conditions
2. Design Coverage Analysis
Map requirements to design elements:
- Architecture decisions - System structure
- Component specifications - Module designs
- Interface definitions - API contracts
- Data models - Database schemas
- Workflow diagrams - Process flows
- UML diagrams - Class/sequence/state diagrams
3. Implementation Coverage Analysis
Verify code implements requirements:
- Feature implementation - Functionality exists
- API endpoints - Required interfaces present
- Business logic - Rules implemented
- Data persistence - Storage implemented
- Error handling - Edge cases handled
- Integration points - Connections implemented
4. Test Coverage Analysis
Ensure tests validate requirements:
- Unit tests - Component-level validation
- Integration tests - Interaction validation
- Acceptance tests - Requirement validation
- Scenario tests - User story coverage
- Edge case tests - Boundary condition coverage
- Performance tests - Non-functional validation
Coverage Checking Workflow
Step 1: Extract Requirements
Identify all requirements from source documents.
Step 2: Map to Design Elements
Check if requirements appear in design.
Step 3: Verify Implementation
Check if code implements design.
Step 4: Validate Test Coverage
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.
- 9d ago First seen · 86 lines · 71 tokens per session scan A 6f6be8602281
requirement-coverage-checker is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (252 stars, last pushed 22d ago), licensed Apache-2.0. It adds 71 tokens to every session and 637 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
702-technologies-wiremock
Use when you need framework-agnostic WireMock guidance — stub design, JSON or programmatic mappings, precise request matching, response bodies and faults, classpath fixtures, isolation and reset between tests, verification of calls, dynamic ports and base URLs, and avoiding flaky stubs — without choosing Spring Boot…
321-frameworks-spring-boot-testing-unit-tests
Use when you need to write unit tests for Spring Boot applications — including pure unit tests with @ExtendWith(MockitoExtension.class) for @Service/@Component, slice tests with @WebMvcTest and @MockitoBean for controllers, @JsonTest for JSON serialization, parameterized tests with @CsvSource/@MethodSource, test…
flake-triage
Decide whether a preview the visual-diff bot flagged actually regressed or is simply nondeterministic, using a repeat-render oracle at a single commit. Use when a PR's preview diff reports a changed preview whose source the PR does not touch, or when a render, GIF or filmstrip is suspected of being unstable.
codex-qa
QA the omo Codex Light edition (lazycodex / packages/omo-codex) itself, in strict isolation so ONLY our plugin is exercised, never the user's real /.codex. The first-party method drives the real codex app-server against an isolated CODEXHOME plus a LOCAL mock model (no real API call), and proves a plugin hook fired by…
refactor-safely
Restructure existing code safely without changing externally observable behavior. Composes context, design, architecture, code quality, and testing guardrails into a characterization-first refactoring workflow. Use when the user says 'refactor this', 'clean this up', 'untangle this module', 'move this to the right…
wio
Testing workflow skill for finding high-value test candidates, writing focused tests, generating realistic workloads, reviewing test value, and diagnosing test-suite health. Use for prompts about what to test next, adding or improving tests, reviewing whether a test is worth keeping, low-signal or flaky tests…