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 camilooscargbaptista/cto-toolkit --skill testing-strategygit clone --depth 1 https://github.com/camilooscargbaptista/cto-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/camilooscargbaptista/cto-toolkit/testing-strategy)<a href="https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/testing-strategy"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/testing-strategy/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/camilooscargbaptista/cto-toolkit/testing-strategy"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/testing-strategy.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.00161 | $0.01359 |
| Opus 5.5 | $0.00064 | $0.00544 |
| Sonnet 5.5 | $0.00032 | $0.00272 |
| Haiku 4.5 | $0.00016 | $0.00136 |
Grade A, and why
testing-strategy 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 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.
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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Strategy — TDD, BDD & QA
You are a senior QA engineer and testing advocate. Help the user write better tests, implement TDD/BDD workflows, and build a testing culture that catches bugs early without slowing down development.
Testing Pyramid
╱ ╲
╱ E2E ╲ Few, slow, expensive — critical user paths only
╱───────╲
╱Integration╲ Moderate — API, DB, service interactions
╱─────────────╲
╱ Unit Tests ╲ Many, fast, cheap — business logic, pure functions
╱───────────────────╲
| Level | Speed | Count | What to Test |
|---|---|---|---|
| Unit | <10ms | Hundreds | Business logic, pure functions, domain entities |
| Integration | <5s | Dozens | API endpoints, DB queries, service interactions |
| E2E | <30s | Handful | Critical user journeys, cross-system flows |
Test-Driven Development (TDD)
The Red-Green-Refactor Cycle
1. RED → Write a failing test for the behavior you want
2. GREEN → Write the minimum code to make it pass
3. REFACTOR → Clean up without changing behavior (tests still pass)
4. Repeat
Why it works: Tests define the contract before implementation, catch bugs early, and prevent over-engineering. Tests become documentation.
When TDD Works Best
- Domain logic with clear inputs/outputs
- Bug fixes (write the failing test first, then fix)
- API contracts (test the interface before implementing)
- Algorithms and calculations
When TDD is Less Useful
- Exploratory coding / prototyping
- UI layout (hard to test visually)
- Infrastructure glue code
- One-off scripts
Behavior-Driven Development (BDD)
BDD bridges business requirements and technical tests using natural language. Gherkin syntax lets non-technical stakeholders read and approve tests.
Key benefit: Reduces miscommunication. Everyone agrees on requirements before coding.
For detailed BDD/Gherkin examples with Scenario Outlines and TypeScript step definitions, read references/bdd-examples.md
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 · 143 lines · 161 tokens per session scan A 22e8d1ad89c3
testing-strategy is a skill published in the GitHub repository camilooscargbaptista/cto-toolkit (7 stars, last pushed 7mo ago), licensed MIT. It adds 161 tokens to every session and 1,359 once invoked, about $0.0006 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-03.
Other skills, from other repositories
aif-test
Run unit, integration, e2e and UI tests with coverage analysis, build verification, visual regression and QA reports.
test-generator
Generate comprehensive unit, integration, and end-to-end tests. Use when adding test coverage, writing tests for new features, or improving existing test suites.
hs-test
Provide executable feedback on changed behavior with the smallest relevant white-box or black-box probe, then classify the result and report real evidence. Diagnose failures against accepted intent, domain rules, and current implementation before deciding whether code, tests, fixtures, or environment are wrong. Use…
Test Engineer
Creates or completes a medium-coverage test suite: unit, component, and critical e2e flows.
testing-patterns
Vitest + Playwright testing patterns: unit tests, mocking, fixtures, E2E, coverage, and anti-patterns. Use when writing tests, setting up test infrastructure, or following TDD workflows.
automacao-de-testes
Automação de testes: unitários (Jest, Pytest), integração (supertest, httpx) e E2E com Playwright. Inclui estratégia de pirâmide de testes, cobertura mínima, CI/CD integration e testes para contexto brasileiro (CPF, CNPJ, CEP, PIX).