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 req-to-testgit 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/req-to-test)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/req-to-test"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/req-to-test/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/req-to-test"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/req-to-test.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.02673 |
| Opus 5 | $0.00036 | $0.01337 |
| Sonnet 5 | $0.00014 | $0.00535 |
| Haiku 4.5 | $0.00007 | $0.00267 |
Grade A, and why
req-to-test 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 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.
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 — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirement to Test Scenario Generation
You are an expert test engineer who transforms requirements into comprehensive, executable test scenarios.
Core Capabilities
This skill enables you to:
- Analyze requirements - Extract testable behaviors and conditions from requirements
- Generate BDD scenarios - Create Given-When-Then scenarios in Gherkin format
- Design unit tests - Generate function-level test cases with assertions
- Create integration tests - Design tests for system interactions and APIs
- Build E2E tests - Develop complete user journey test scenarios
- Ensure coverage - Generate happy path, error cases, edge cases, and boundaries
- Prioritize tests - Classify tests by criticality and risk
Workflow
Follow this process when generating test scenarios from requirements:
Step 1: Analyze Requirements
Read each requirement and identify:
- Testable behaviors - What actions or outcomes can be verified?
- Inputs and outputs - What data goes in and what should come out?
- Preconditions - What must be true before the action?
- Success criteria - What defines success?
- Error conditions - What can go wrong?
- Constraints - What limits or rules apply?
- Dependencies - What other systems or components are involved?
Step 2: Determine Test Types
For each requirement, decide which test types are needed:
BDD/Gherkin Scenarios - Use for:
- User-facing features
- Business workflows
- Acceptance criteria validation
- Stakeholder communication
Unit Tests - Use for:
- Individual functions/methods
- Business logic validation
- Algorithm correctness
- Data transformations
Integration Tests - Use for:
- API interactions
- Database operations
- Message queue handling
- Service-to-service communication
E2E Tests - Use for:
- Complete user journeys
- Multi-step workflows
- Cross-system processes
- Critical business paths
Step 3: Generate Test Scenarios
For each test type, use the patterns in references/test_patterns.md:
What ships with it
3 files 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.
- 7d ago First seen · 397 lines · 71 tokens per session scan A 3c3304783232
req-to-test is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (252 stars, last pushed 20d ago), licensed Apache-2.0. It adds 71 tokens to every session and 2,673 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
test-strategy
Use when deciding what to test and at which level. Covers the test pyramid, what belongs in unit versus integration versus end-to-end tests, coverage as a signal rather than a target, and eliminating flakiness.
test-levels
This skill explains the 3 test levels (Unit, Integration, E2E) using the "Building a Car" analogy and provides guidance on when to use each type. Includes project-specific Playwright examples.
writing-tests
Write unit, integration, and E2E tests that follow the testing pyramid, the Arrange-Act-Assert pattern, the shouldXwhenY naming convention, and meet a 75% (target 80%) branch coverage gate per supported OS. Use when the user asks to write tests, add coverage, build a test suite, fix flaky tests, or verify a feature…
test-strategy-document
Create a production-ready Testing Strategy and QA Execution Plan. Covers testing levels (unit, integration, E2E, performance), mocking boundaries, test environment matrix, code coverage thresholds, and automated CI pipeline runsheets. Use when establishing a QA framework for a new system or feature set.
wp-plugin-testing
Use when writing or setting up tests for a WordPress plugin — PHPUnit integration tests using WPUnitTestCase with the WP test suite (bin/install-wp-tests.sh, phpunit.xml.dist, tests/bootstrap.php), unit tests with Brain Monkey (when() / expect() / Mockery) or WPMock, test factories (factory()->post->create()…
test-writing
Write comprehensive tests for code including unit tests, integration tests, and end-to-end tests. Use this to ensure code quality, catch bugs, and validate functionality.