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 fugazi/test-automation-skills-agents --skill qa-manual-istqbgit clone --depth 1 https://github.com/fugazi/test-automation-skills-agentsWrote 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/fugazi/test-automation-skills-agents/qa-manual-istqb)<a href="https://agentmods.dev/skills/fugazi/test-automation-skills-agents/qa-manual-istqb"><img src="https://agentmods.dev/badge/skills/fugazi/test-automation-skills-agents/qa-manual-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/fugazi/test-automation-skills-agents/qa-manual-istqb"><img src="https://agentmods.dev/badge/skills/fugazi/test-automation-skills-agents/qa-manual-istqb.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.00084 | $0.02879 |
| Opus 5 | $0.00042 | $0.01439 |
| Sonnet 5 | $0.00017 | $0.00576 |
| Haiku 4.5 | $0.00008 | $0.00288 |
Grade A, and why
qa-manual-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 12d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Test Design & ISTQB Artifacts
Complete ISTQB Foundation Level (CTFL) aligned workflow for QA test engineers covering: Test Planning → Test Analysis → Test Design → Test Implementation → Test Execution → Test Completion
When to Use This Skill
- Drafting ready-to-fill QA deliverables from requirements, user stories, or acceptance criteria
- Creating or reviewing test plans and test strategies
- Generating test conditions and test cases from requirements
- Applying test design techniques (EP, BVA, decision tables, state transitions, use cases)
- Writing bug reports and managing defect lifecycle
- Building regression suites with risk-based selection
- Creating traceability matrices (requirements ↔ tests ↔ defects)
- Conducting exploratory testing sessions with charters
- Estimating test effort using ISTQB techniques
- Reviewing testware through static testing practices
- Selecting automation candidates and preparing traceable Playwright scaffolds
Do NOT Use For
- Authoring/maintaining versioned Playwright spec code (use
playwright-e2e-testing). - Selenium/Java test authoring (use
webapp-selenium-testing). - Driving a live browser to debug (use
playwright-cli) or governing an existing regression suite's CI (useplaywright-regression-testing). - Adversarial strategy critique — that is the
grill-me-qaskill's purpose; this skill produces artifacts, it does not interrogate them.
Prerequisites
| Requirement | Notes |
|---|---|
| Node.js 18+ | Required for CLI script and Playwright |
| Playwright | npm init playwright@latest for automation |
| Text editor | For creating/editing markdown and CSV artifacts |
| Git | Recommended for testware version control |
Quick Start (choose one)
- Create a test plan: use
templates/test-plan.mdas a starting point. - Create a test summary report: use
templates/test-summary-report.md. - Generate test cases: use
templates/test-cases.csvand fill it from the test basis (requirements, user stories, acceptance criteria). - Create a bug report: use
templates/bug-report.md. - Create a bug log: use
templates/bug-log.csv. - Create traceability: use
templates/traceability-matrix.csv. - Build a regression suite definition: use
templates/regression-suite.md. - Scaffold Playwright tests: use
templates/playwright-spec.tsand adapt to the system under test. - Run exploratory testing: use
templates/exploratory-charter.mdto timebox and capture outcomes.
What ships with it
27 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.
- LICENSE.txt 1.0 KB
- references/automation-playwright-best-practices.md 1.2 KB
- references/bug-report-quality.md 876 B
- references/defect-lifecycle.md 759 B
- references/experience-based-techniques.md 9.2 KB
- references/istqb-glossary.md 11 KB
- references/regression-suite-strategy.md 1.1 KB
- references/risk-based-testing.md 9.6 KB
- references/static-testing.md 5.6 KB
- references/test-design-techniques.md 7.6 KB
- references/test-estimation.md 8.7 KB
- references/test-levels-types.md 10 KB
- references/test-monitoring-metrics.md 9.1 KB
- references/test-process-and-deliverables.md 1.2 KB
- scripts/qa_artifacts.mjs 7.9 KB runs code
- templates/bug-log.csv 203 B
- templates/bug-report.md 991 B
- templates/exploratory-charter.md 800 B
- templates/playwright-spec.ts 510 B runs code
- templates/regression-suite.md 1.2 KB
- templates/risk-assessment-matrix.md 7.1 KB
- templates/test-cases.csv 1.9 KB
- templates/test-conditions.md 3.6 KB
- templates/test-environment-checklist.md 7.6 KB
- templates/test-plan.md 15 KB
- templates/test-summary-report.md 950 B
- templates/traceability-matrix.csv 298 B
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.
- 12d ago First seen · 237 lines · 84 tokens per session scan A 69ad68e060c9
qa-manual-istqb is a skill published in the GitHub repository fugazi/test-automation-skills-agents (234 stars, last pushed 9d ago), licensed MIT. It adds 84 tokens to every session and 2,879 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-08-30.
Other skills, from other repositories
unit-test
A Go testing workflow for writing unit tests: small tests that check individual functions or components. It supports table-driven cases, where many inputs and expected results are organised in one test, and subtests.
api-integration-test
Create, maintain, and run gated Go integration tests for internal APIs and service-to-service clients (HTTP/gRPC). Use for endpoint verification, contract checks with real runtime config, opt-in execution, timeout/retry safety, and integration failure triage in Go services.
load-test
Performance load testing specialist for writing k6/vegeta/wrk scripts, defining SLOs, modeling scenarios (spike/soak/stress/breakpoint), analyzing results, and identifying bottlenecks. ALWAYS use when writing load test scripts, reviewing test results, designing test scenarios, setting performance SLOs, or diagnosing…
e2e-test
Design, maintain, and execute reliable end-to-end tests for critical user journeys with Agent Browser as first choice for exploration and Playwright as the preferred code path for suites and CI. Use for E2E strategy, journey coverage, flaky test triage, artifact collection, CI gating, regression prevention, and…
fuzzing-test
A Go testing guide for generating fuzz tests, which repeatedly try varied inputs to find crashes and unexpected behavior. It first checks whether the code is suitable for fuzzing.
tdd-workflow
Enforce practical Test-Driven Development for code changes in Go services. Use for new features, bug fixes, refactors, API changes, and new modules. Requires Red-Green-Refactor evidence, defect-hypothesis-driven tests, killer cases, and coverage gates (line + risk-path).