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 daffy0208/ai-dev-standards --skill testing-strategistgit clone --depth 1 https://github.com/daffy0208/ai-dev-standardsWrote 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/daffy0208/ai-dev-standards/testing-strategist)<a href="https://agentmods.dev/skills/daffy0208/ai-dev-standards/testing-strategist"><img src="https://agentmods.dev/badge/skills/daffy0208/ai-dev-standards/testing-strategist/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/daffy0208/ai-dev-standards/testing-strategist"><img src="https://agentmods.dev/badge/skills/daffy0208/ai-dev-standards/testing-strategist.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00051 | $0.05735 |
| Opus 5 | $0.00026 | $0.02867 |
| Sonnet 5 | $0.00010 | $0.01147 |
| Haiku 4.5 | $0.00005 | $0.00573 |
Grade A, and why
Testing Strategist 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 7d 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 — 933 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Strategist
Test the right things at the right level - write tests that give you confidence to ship.
Core Principle
The Testing Pyramid: 70% unit tests, 20% integration tests, 10% E2E tests.
Tests should be:
- Fast - Run in milliseconds (unit) to seconds (integration) to minutes (E2E)
- Isolated - Test one thing at a time
- Repeatable - Same input = same output
- Self-checking - Pass/fail automatically, no manual verification
- Timely - Written alongside code (or before, with TDD)
The Testing Pyramid
/\
/ \ E2E Tests (10%)
/----\ - Slow, brittle, expensive
/ \ - Test critical user journeys
/--------\ - Example: "User can complete checkout"
/ \
/------------\ Integration Tests (20%)
/ \ - Medium speed, test components together
/----------------\ - Example: "API endpoint returns correct data"
/ \
/--------------------\ Unit Tests (70%)
/______________________\ - Fast, isolated, test functions/components
- Example: "calculateTotal returns sum"
Why This Ratio?
- Unit tests: Fast feedback, pinpoint bugs precisely, easy to maintain
- Integration tests: Ensure components work together, catch interface issues
- E2E tests: Verify actual user flows, catch UI bugs, but slow and brittle
Level 1: Unit Tests (70%)
What to Test
Test individual functions, components, or classes in isolation.
Good candidates:
- ✅ Business logic functions (calculations, validation, transformations)
- ✅ Utility functions (formatDate, parseUrl, etc.)
- ✅ React components (rendering, props, state)
- ✅ Hooks (custom React hooks)
- ✅ Pure functions (same input = same output)
Skip:
- ❌ Third-party libraries (assume they work)
- ❌ Framework internals (React, Next.js)
- ❌ Simple getters/setters with no logic
Unit Test Examples
Testing Business Logic (Jest + TypeScript)
What ships with it
2 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.
- 7d ago First seen · 933 lines · 51 tokens per session scan A 104b174797b1
Testing Strategist is a skill published in the GitHub repository daffy0208/ai-dev-standards (36 stars, last pushed 8mo ago), licensed MIT. It adds 51 tokens to every session and 5,735 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
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.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
prd-auto-test-loop
A testing workflow driven by a product requirements document (PRD), which describes what a software version should do. It turns acceptance criteria into unit, integration, and end-to-end tests, then records the plan and results.
test-automation-expert
Comprehensive test automation specialist covering unit, integration, and E2E testing strategies. Expert in Jest, Vitest, Playwright, Cypress, pytest, and modern testing frameworks. Guides test pyramid design, coverage optimization, flaky test detection, and CI/CD integration. Activate on 'test strategy', 'unit tests'…