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 siberiacancode/agent-skills --skill testing-best-practicesgit clone --depth 1 https://github.com/siberiacancode/agent-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/siberiacancode/agent-skills/testing-best-practices)<a href="https://agentmods.dev/skills/siberiacancode/agent-skills/testing-best-practices"><img src="https://agentmods.dev/badge/skills/siberiacancode/agent-skills/testing-best-practices/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/siberiacancode/agent-skills/testing-best-practices"><img src="https://agentmods.dev/badge/skills/siberiacancode/agent-skills/testing-best-practices.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.00047 | $0.01826 |
| Opus 5.5 | $0.00019 | $0.00730 |
| Sonnet 5.5 | $0.00009 | $0.00365 |
| Haiku 4.5 | $0.00005 | $0.00183 |
Grade A, and why
testing-best-practices 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 16d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Best Practices
Practical QA guidance for turning product behavior, requirements, and code paths into useful checks. Use this skill for manual test cases, test plans, coverage reviews, automation scenarios, unit tests, Playwright browser and component integration tests, locators, /unit-test-grill, /integration-test-grill, and /testcase-grill.
The central idea is not a specific framework. The central idea is testing discipline:
- Start from the user-visible or public contract: what must work, what may fail, and what must never happen.
- Choose the right testing format for the risk: exploratory notes, manual test cases, regression checklist, unit coverage, integration scenario, or automation task.
- Make every check prove a meaningful behavior, requirement, branch, state transition, error path, or cleanup guarantee.
- Keep coverage focused. Test independent dimensions separately, avoid noisy Cartesian products, and skip arbitrary edge values that only retest the platform.
- Preserve project reality by reading nearby tests, existing QA artifacts, product flows, schemas, and automation conventions before adding new structure.
- Treat integration-test locators and test data as maintained testing APIs, changing schema, implementation, and affected checks together.
Use the specific rule files after choosing the testing subject. The current detailed rules cover automated unit tests, semantic integration locators, and repository-stored product test cases; for other QA formats, apply the core defaults in this file and keep the output concrete enough for a tester or automation engineer to execute.
When to Apply
Reference these guidelines when:
- Creating manual test cases, smoke checks, regression suites, acceptance scenarios, or exploratory charters.
- Generating, revising, reviewing, or reorganizing structured test cases stored in the repository's test-case catalog.
- Planning or reviewing automation coverage for application behavior.
- Adding or reviewing automated tests for code.
- Looking for missing behavioral coverage, branch coverage, state transitions, cleanup checks, or error paths.
- Deciding how to name, order, and scope checks inside a test file or QA checklist.
- Creating or reviewing a locator for integration tests, including the semantic name, schema path, JSX attribute, and affected checks.
- Invoking
/unit-test-grillto turn code behavior into a checklist without writing test code. - Invoking
/integration-test-grillto map confirmed product cases to browser or component automation without writing test code. - Invoking
/testcase-grillto turn a page or block into a list of owned test cases without writing them into the catalog.
What ships with it
29 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.
- AGENTS.md 21 KB
- metadata.json 514 B
- README.md 3.5 KB
- rules/_sections.md 1.5 KB
- rules/_template.md 367 B
- rules/integration-test-browser.md 2.4 KB
- rules/integration-test-component.md 1.8 KB
- rules/integration-test-conventions.md 7.9 KB
- rules/integration-test-grill.md 5.2 KB
- rules/integration-test-locator-testids.md 6.3 KB
- rules/integration-test-mocks.md 2.4 KB
- rules/integration-test-server.md 2.8 KB
- rules/integration-test-setup.md 3.5 KB
- rules/references/hook-listeners.md 3.1 KB
- rules/references/hook-web-api.md 2.9 KB
- rules/testcase-content.md 5.6 KB
- rules/testcase-conventions.md 5.9 KB
- rules/testcase-file-structure.md 2.4 KB
- rules/testcase-grill.md 6.3 KB
- rules/testcase-naming.md 1016 B
- rules/testcase-preconditions.md 2.5 KB
- rules/testcase-testit-xlsx-export.md 3.1 KB
- rules/testcase-testit-xlsx-read.md 2.4 KB
- rules/unit-test-conventions.md 6.3 KB
- rules/unit-test-function.md 894 B
- rules/unit-test-grill.md 4.7 KB
- rules/unit-test-react-component-compound.md 2.3 KB
- rules/unit-test-react-component-standalone.md 2.3 KB
- rules/unit-test-react-hook.md 2.8 KB
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.
- 16d ago Changed · +2 lines 960123f6add7
- 1mo ago Changed 8927f5498289
- 1mo ago Changed · +7 lines · +3 tokens per session e0872c30ffb3
- 1mo ago Changed · +11 lines a6bbffbcda5d
- 1mo ago First seen · 75 lines · 44 tokens per session scan A cd3f527369cc
testing-best-practices is a skill published in the GitHub repository siberiacancode/agent-skills (23 stars, last pushed 17d ago), licensed MIT. It adds 47 tokens to every session and 1,826 once invoked, about $0.0002 per session on Opus 5.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-04.
Other skills, from other repositories
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
test-building-blocks
Test building block catalog — typed patterns for Storybook play-function tests, Vitest hook tests, Vitest unit tests, MSW handlers, and test data fixtures. Read the relevant rule file before writing or modifying any test, handler, or fixture. Covers: deciding which kind of test to write, authoring a new test from…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
axiom-testing
Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.