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 agentmods add skills/softspark/ai-toolkit/testing-patternsnpx skills add softspark/ai-toolkit --skill testing-patternsgit clone --depth 1 https://github.com/softspark/ai-toolkitWrote 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/softspark/ai-toolkit/testing-patterns)<a href="https://agentmods.dev/skills/softspark/ai-toolkit/testing-patterns"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/testing-patterns.svg" alt="Measured on agentmods" 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 | $0.00052 | $0.01258 |
| Opus 5 | $0.00026 | $0.00629 |
| Sonnet 5 | $0.00010 | $0.00252 |
| Haiku 4.5 | $0.00005 | $0.00126 |
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 yesterday.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Patterns Skill
Test Structure (AAA Pattern)
def test_function_does_expected_thing():
"""Test description explaining what and why."""
# Arrange - Set up test data and preconditions
input_data = {"key": "value"}
expected = "result"
# Act - Execute the code under test
result = function_under_test(input_data)
# Assert - Verify the outcome
assert result == expected
Test Organization
tests/
├── conftest.py # Shared fixtures
├── unit/ # Unit tests (isolated)
│ ├── test_search_core.py
│ └── test_utils.py
├── integration/ # Integration tests
│ └── test_api.py
└── e2e/ # End-to-end tests
└── test_workflow.py
Quality Targets
| Metric | Target |
|---|---|
| Coverage | >70% overall |
| New code | 100% |
| Core modules | >80% |
| No flaky tests | 0 |
Language-Specific References
| Language | Reference | Key Topics |
|---|---|---|
| Python | reference/python-pytest.md | Fixtures, mocking, parametrize, markers, conftest, running tests |
| TypeScript | reference/typescript-vitest.md | Vitest/Jest, React Testing Library, mocking, running tests |
| PHP | reference/php-phpunit.md | PHPUnit test cases, mocking, running tests |
| Go | reference/go-testing.md | Table-driven tests, testify mocking, running tests |
| Flutter/Dart | reference/flutter-testing.md | Widget tests, unit tests, running tests |
For Python pytest patterns, see reference/python-pytest.md.
For TypeScript Vitest/Jest patterns, see reference/typescript-vitest.md.
For PHP PHPUnit patterns, see reference/php-phpunit.md.
For Go testing patterns, see reference/go-testing.md.
What ships with it
5 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.
- yesterday First seen · 111 lines · 52 tokens per session scan A 838e60336ca9
testing-patterns is a skill published in the GitHub repository softspark/ai-toolkit (168 stars, last pushed yesterday), licensed Apache-2.0. It adds 52 tokens to every session and 1,258 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
ios-test
XCTest patterns for unit tests, UI tests, and SwiftData testing with in-memory containers under Swift 6 strict concurrency, plus test performance budgets. Use when writing or fixing tests, setting up test targets, testing SwiftData models, or planning CI test suites. Trigger on "write a test", "unit test", "XCTest"…
testing-strategies
Systematic testing for confidence without over-testing — the right test at the right level.
converter-qa
Test harness for validating converter outputs with 284 assertions across all converter muscles.
testing-patterns
Cross-language testing strategies and patterns. Triggers on: test pyramid, unit test, integration test, e2e test, TDD, BDD, test coverage, mocking strategy, test doubles, test isolation.
ds-test
Universal test skill — generate, update, run, and fix tests for any stack. Use when writing, repairing, or running tests, or improving coverage.
adept-writing-tests
How to write tests in the adept Go codebase — table-driven tests with testify, golden fixtures under testdata/, the cmd/adept e2e harness, temp-dir/HOME isolation, and coverage gates. Apply when adding or changing Go tests here. (matches: /test.go).