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 yonatangross/orchestkit --skill testing-patternsgit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/testing-patterns)<a href="https://agentmods.dev/skills/yonatangross/orchestkit/testing-patterns"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/testing-patterns/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/yonatangross/orchestkit/testing-patterns"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/testing-patterns.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.00059 | $0.00508 |
| Opus 5.5 | $0.00024 | $0.00203 |
| Sonnet 5.5 | $0.00012 | $0.00102 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
testing-patterns 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 29d 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.
What it actually says
Testing Patterns (Redirect)
This skill was split into 5 focused sub-skills in v7.2.0. Use the appropriate sub-skill below.
Sub-Skills
| Sub-Skill | Focus | When to Use |
|---|---|---|
ork:testing-unit |
Unit tests, AAA pattern, fixtures, mocking, factories | Isolated business logic tests |
ork:testing-e2e |
Playwright, page objects, visual regression, a11y | Browser-based end-to-end tests |
ork:testing-integration |
API endpoints, database, contract testing | Cross-boundary integration tests |
ork:testing-llm |
LLM mocking, DeepEval/RAGAS, structured output | AI/ML evaluation and testing |
ork:testing-perf |
k6, Locust, pytest-xdist, benchmark | Performance and load testing |
Quick Reference
testing-unit # Unit testing patterns
testing-e2e # End-to-end with Playwright
testing-integration # API and database integration
testing-llm # LLM evaluation patterns
testing-perf # Performance and load testing
Related Skills
ork:testing-unit— Unit testing: AAA pattern, fixtures, mocking, factoriesork:testing-e2e— E2E testing: Playwright, page objects, visual regressionork:testing-integration— Integration testing: API endpoints, database, contractsork:testing-llm— LLM testing: mock responses, DeepEval/RAGAS evaluationork:testing-perf— Performance testing: k6, Locust, pytest-xdist
What ships with it
4 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.
- 29d ago Changed 01fe9521887b
- 1mo ago Changed 712e9f804993
- 1mo ago First seen · 47 lines · 59 tokens per session scan A 1a4042d45c1a
testing-patterns is a skill published in the GitHub repository yonatangross/orchestkit (297 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 508 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-05.
Other skills, from other repositories
continuous-testing
Continuous test-driven development loop — after every code change, builds the project, starts the server, and runs Unit Tests, Integration Tests, and System Tests. Applies on top of microprofile-server skill. Use during development when you want full verification after each change. Triggers on "continuous testing"…
pn-testing-strategy
Testing strategy and pyramid. Unit/integration/E2E ratio, Vitest vs Playwright vs MSW, contract testing, and test-environment setup. Use when defining or reviewing a project's testing approach.
testing-patterns
Testing patterns and principles. Unit, integration, mocking strategies.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.