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 petrkindlmann/qa-skills --skill test-case-managementgit clone --depth 1 https://github.com/petrkindlmann/qa-skillsWrote 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/petrkindlmann/qa-skills/test-case-management)<a href="https://agentmods.dev/skills/petrkindlmann/qa-skills/test-case-management"><img src="https://agentmods.dev/badge/skills/petrkindlmann/qa-skills/test-case-management/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/petrkindlmann/qa-skills/test-case-management"><img src="https://agentmods.dev/badge/skills/petrkindlmann/qa-skills/test-case-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00203 | $0.04877 |
| Opus 5.5 | $0.00081 | $0.01951 |
| Sonnet 5.5 | $0.00041 | $0.00975 |
| Haiku 4.5 | $0.00020 | $0.00488 |
Grade A, and why
test-case-management scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
The four tools are easy to cross-wire. Summary — full curl/GraphQL bodies in How it starts
The opening of the file, as written. The whole thing — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Route
| Request | Go to |
|---|---|
| Write one well-formed case from an AC | Test-Case Anatomy |
| Bulk-generate cases from a story | Bulk Authoring + tool section |
| "Lint these steps / are these verifiable?" | Ambiguous-Step Linting + references/linting.md |
| TestRail / Xray / Zephyr / Qase API payload | Tool Payloads + references/tool-apis.md |
| CSV to import into TestRail | references/import-and-traceability.md (CSV section) |
| Organize suites/sections | references/import-and-traceability.md (organization) |
| Requirements ↔ tests, coverage gaps | Traceability + references/import-and-traceability.md |
| Manual → automation decision | Automation Graduation |
Discovery Questions
First, check .agents/qa-project-context.md in the project root for the tool, project keys,
and conventions; skip anything answered there. If it's missing, suggest creating one with the
qa-project-context skill. Then clarify:
- Which tool — TestRail, Xray, Zephyr Scale, or Qase? Each has a different API auth scheme, endpoint shape, and step-field name. Getting this wrong produces payloads that 401 or 400.
- TestRail only: single-repository mode or multiple suites? Changes whether cases live under
sections in one suite or in separate suites — affects every
section_idand the org plan. - Xray/Zephyr only: Jira Cloud or Server/DC? Cloud and Server use different base paths and auth. This skill targets Cloud; Server uses different endpoints.
- Source of the cases — acceptance criteria, a user story, a free-form feature? Drives how many cases to generate and how to split rules.
- Do you need requirement traceability? If yes, capture the Jira/requirement issue keys now so cases link on creation rather than being back-filled.
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.
- 1mo ago First seen · 374 lines · 203 tokens per session scan A bae4d8c655ce
test-case-management is a skill published in the GitHub repository petrkindlmann/qa-skills (217 stars, last pushed 6d ago), licensed MIT. It adds 203 tokens to every session and 4,877 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
CI Pipeline Optimizer
Optimize CI test pipelines through intelligent test splitting, parallelization, caching strategies, and selective test execution based on code changes.
Flaky Test Quarantine
Detect, quarantine, and systematically fix flaky tests with automated retry analysis, root cause categorization, and CI pipeline integration for test reliability.
CI/CD Pipeline Advanced
Expert-level CI/CD pipeline skill for test automation. Covers GitHub Actions, Jenkins, GitLab CI, Azure DevOps, parallel execution, matrix strategies, caching, artifact management, and deployment gates.
Checkly Monitoring as Code
Teach agents to build synthetic monitoring as code with Checkly, including Playwright browser checks, API checks, alerting, and CI deploy workflows.
CI Test Sharding Parallelization
Teach agents to shard and parallelize Playwright, Jest, and pytest suites in CI to reduce wall-clock time while merging reports reliably.
Advanced Chaos Engineering
Advanced chaos engineering patterns using Chaos Monkey, Litmus, and Gremlin for testing distributed system resilience under failure conditions.