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 javalenciacai/QASkills --skill test-design-istqbgit clone --depth 1 https://github.com/javalenciacai/QASkillsWrote 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/javalenciacai/qaskills/test-design-istqb)<a href="https://agentmods.dev/skills/javalenciacai/qaskills/test-design-istqb"><img src="https://agentmods.dev/badge/skills/javalenciacai/qaskills/test-design-istqb/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/javalenciacai/qaskills/test-design-istqb"><img src="https://agentmods.dev/badge/skills/javalenciacai/qaskills/test-design-istqb.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.00036 | $0.01027 |
| Opus 5 | $0.00018 | $0.00513 |
| Sonnet 5 | $0.00007 | $0.00205 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
test-design-istqb 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 11d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Design - ISTQB Techniques
Expert skill for designing comprehensive test cases using ISTQB Foundation Level test design techniques.
When to Use
Use this skill when you need to:
- Design test cases from requirements
- Apply black-box testing techniques
- Create test data specifications
- Ensure comprehensive test coverage
- Generate test scenarios for positive, negative, and edge cases
ISTQB Test Design Techniques
1. Equivalence Partitioning
What it is: Divide input domains into classes where all members should be treated the same.
How to apply:
- Identify all inputs and outputs
- Determine valid and invalid partitions
- Create one test case per partition
- Cover both valid and invalid classes
Example:
Requirement: Age must be 18-65
Partitions:
- Invalid: < 18 (e.g., 17)
- Valid: 18-65 (e.g., 30)
- Invalid: > 65 (e.g., 66)
2. Boundary Value Analysis
What it is: Test at the edges of equivalence partitions where defects often hide.
How to apply:
- Identify boundaries in requirements
- Test: min-1, min, min+1, max-1, max, max+1
- Focus on limits, ranges, and thresholds
Example:
Requirement: Password 8-20 characters
Test values: 7, 8, 9, 19, 20, 21 characters
3. Decision Tables
What it is: Test combinations of conditions and their resulting actions.
How to apply:
- Identify conditions (inputs/states)
- List possible actions (outputs/behaviors)
- Create table with all meaningful combinations
- Generate test cases from each column
Example:
Condition 1: Premium customer? (Y/N)
Condition 2: Order > $100? (Y/N)
| Premium | Order>$100 | Discount |
|---------|-----------|----------|
| Y | Y | 20% |
| Y | N | 10% |
| N | Y | 10% |
| N | N | 0% |
= 4 test cases
4. State Transition Testing
What it is: Test how system behavior changes based on state and events.
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.
- 11d ago First seen · 172 lines · 36 tokens per session scan A 2277ac4b18d1
test-design-istqb is a skill published in the GitHub repository javalenciacai/QASkills (5 stars, last pushed 7mo ago), licensed MIT. It adds 36 tokens to every session and 1,027 once invoked, about $0.0002 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
qa-expert
Expert-level quality assurance, testing strategies, automation, and QA processes. Use when the user mentions testing, test automation, quality assurance, or Selenium, or when the task involves Testing Types, QA Processes, Test Strategy, or Defect Management.
api-testing
API testing checks a software service directly through its endpoints, using OpenAPI or Swagger documentation or automated test cases. It can produce and run scripts that test requests and responses.
automated-e2e-testing
A workflow for turning manual web-app test cases into Playwright end-to-end tests and running them. End-to-end tests check a complete user flow through the website.
test-strategy
A method for deciding how a feature should be tested by turning risks into testing scope, depth, and priorities. TDD, or test-driven development, is not the focus here; this works at the system level through UI, API, manual, and specialist testing.
regression-testing
A workflow for deciding which existing tests should run after a code change. Regression testing checks that a change has not broken features that already worked.
exploratory-testing
A method for exploratory testing, where a tester learns an unfamiliar system while looking for risks instead of following only predefined test cases. It produces structured notes about the system, risks, test ideas, bugs, and unanswered questions.