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 oumaimah-QA/QIOS --skill qa-test-designergit clone --depth 1 https://github.com/oumaimah-QA/QIOSWrote 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/oumaimah-qa/qios/qa-test-designer)<a href="https://agentmods.dev/skills/oumaimah-qa/qios/qa-test-designer"><img src="https://agentmods.dev/badge/skills/oumaimah-qa/qios/qa-test-designer/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/oumaimah-qa/qios/qa-test-designer"><img src="https://agentmods.dev/badge/skills/oumaimah-qa/qios/qa-test-designer.svg" alt="Reviewed on agentmods" width="80" 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.00125 | $0.00908 |
| Opus 5 | $0.00063 | $0.00454 |
| Sonnet 5 | $0.00025 | $0.00182 |
| Haiku 4.5 | $0.00013 | $0.00091 |
Grade A, and why
qa-test-designer 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 8d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Test Designer
Purpose
Transform a User Story, acceptance criteria, or feature description into a structured, complete, ready-to-execute test plan — with risk levels, flags, and coverage analysis.
Input Accepted
- User Story format:
As a [role] / I want [action] / So that [benefit] - Acceptance criteria (bullet points or Given/When/Then)
- Jira ticket content (paste the full description)
- Feature description in plain language
- Epic or business requirement document excerpt
Analysis Process
Step 1 — Parse and Structure
Extract:
Feature : What is being built?
Actor(s) : Who uses it? Which roles?
Goal : What outcome is expected?
Business Rules: Constraints, limits, conditions
Data : Input fields, output fields, data types
Risks : What can go wrong? What is the impact?
Dependencies : Other features, services, or data required
Flag immediately — do not assume:
[MISSING] : Information needed to test but not provided
[AMBIGUOUS] : Requirement that is unclear or contradictory
[ASSUMPTION] : What is being assumed to proceed
Step 2 — Coverage Strategy
Define which test types are needed:
Functional → Core behavior: does it do what the spec says?
Boundary → Min/max values, limits, thresholds
Negative → Wrong input, missing data, broken flows
Integration → Interaction with other components or services
Security → Auth, permissions, data access
Performance → Response time, throughput (flag if needed, mark as out of scope if not)
Step 3 — Generate Test Cases
Use the structure from ../../_shared/test-case-template.md.
Minimum per feature:
- 1 happy path (P1)
- 1 negative per business rule (P1)
- 1 boundary per numeric/date field (P2)
- 1 auth/permission check if applicable (P1 — CRITICAL)
Output Format
Test Plan Header
═══════════════════════════════════════════
TEST PLAN
Feature : [Feature Name]
Reference : [US-XXX / JIRA-XXX]
Date : [Date]
Total Cases : [N]
Coverage : Functional ✅ Boundary ✅ Negative ✅ Security ⚠️
Flags : [N] MISSING [N] AMBIGUOUS [N] ASSUMPTION
═══════════════════════════════════════════
What ships with it
5 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.
- 8d ago First seen · 129 lines · 125 tokens per session scan A 52774d3d5a06
qa-test-designer is a skill published in the GitHub repository oumaimah-QA/QIOS (3 stars, last pushed 1mo ago), licensed MIT. It adds 125 tokens to every session and 908 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-31.
Other skills, from other repositories
BDD/Cucumber Patterns
Behavior-Driven Development skill using Cucumber, covering feature files, step definitions, Gherkin best practices, data tables, scenario outlines, and hooks.
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
bruno
Comprehensive operational skill specification for Anthropic Claude to automate, script, troubleshoot, and optimize Bruno API Client, Bru markup language (.bru), CLI runner (@usebruno/cli), and CI/CD test pipelines.
BDD Gherkin Testing Patterns
Behavior-Driven Development with Gherkin syntax, step definitions, scenario outlines, data tables, and living documentation generation.
Playwright API Testing
API testing with Playwright APIRequestContext for REST and GraphQL endpoints.
Playwright E2E Testing
Comprehensive Playwright end-to-end testing patterns with Page Object Model, fixtures, and best practices.