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/bdiasti/maestro-bundle-cli/testing-strategynpx skills add bdiasti/maestro-bundle-cli --skill testing-strategygit clone --depth 1 https://github.com/bdiasti/maestro-bundle-cliWhat 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.00038 | $0.01612 |
| Opus 5 | $0.00019 | $0.00806 |
| Sonnet 5 | $0.00008 | $0.00322 |
| Haiku 4.5 | $0.00004 | $0.00161 |
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 3d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Strategy
Implement the testing pyramid with domain unit tests, integration tests for repositories, and e2e tests for API endpoints, following consistent naming and fixture patterns.
When to Use
- Writing tests for new features or bug fixes
- Setting up test infrastructure for a new project
- Improving test coverage on existing code
- Reviewing test quality and naming conventions
- Configuring CI/CD test pipelines
Available Operations
- Write unit tests for domain entities and value objects
- Write integration tests for repositories and external services
- Write e2e tests for API endpoints
- Configure test fixtures and factories
- Run tests and measure coverage
- Set up test pipelines in CI/CD
Multi-Step Workflow
Step 1: Understand the Testing Pyramid
/ E2E \ Few, slow, expensive
/ Integr. \ Moderate count
/ Unit Tests \ Many, fast, cheap
- Unit tests: Test domain logic in isolation. No database, no HTTP, no external services.
- Integration tests: Test adapters (repositories, clients) against real infrastructure.
- E2E tests: Test full API request/response cycles.
Step 2: Write Unit Tests for Domain Entities
Test business rules without any infrastructure dependency.
# tests/domain/test_demand.py
import pytest
class TestDemand:
def test_should_decompose_new_demand(self):
demand = Demand(id=DemandId.generate(), description="Create CRUD")
planner = FakePlanner(tasks=[Task(...), Task(...)])
tasks = demand.decompose(planner)
assert len(tasks) == 2
assert demand.status == DemandStatus.PLANNED
def test_should_reject_decompose_if_already_planned(self):
demand = Demand(id=DemandId.generate(), description="Create CRUD")
demand.decompose(FakePlanner(tasks=[Task(...)]))
with pytest.raises(DemandAlreadyDecomposedException):
demand.decompose(FakePlanner(tasks=[]))
def test_should_not_allow_more_than_20_tasks(self):
demand = Demand(id=DemandId.generate(), description="Mega project")
for i in range(20):
demand.add_task(Task(...))
with pytest.raises(TooManyTasksException):
demand.add_task(Task(...))
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.
- 3d ago First seen · 205 lines · 38 tokens per session scan A 2dfaafca05e6
testing-strategy is a skill published in the GitHub repository bdiasti/maestro-bundle-cli (21 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 1,612 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
testing-patterns
Testing patterns and principles. Unit, integration, mocking strategies.
testing
Writing or debugging tests, choosing unit vs integration style, Postgres/ClickHouse tests, regenerating ClickHouse test schema, or exporting test helpers from packages without pulling test code into production bundles.
detect-flaky-tests
Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM lanes). For each newly-detected flaky test or infra issue, opens a GitHub issue with full evidence and a draft fix PR. Does…
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-flutter
Flutter App のテスト実行・静的解析・フォーマット・テスト記述ガイド.
test
Run tests. Use after code changes to validate. Arguments: unit (default, no GPU), e2e (with models), filter name, or all.