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/ai-debugger-inc/aidb/testing-strategynpx skills add ai-debugger-inc/aidb --skill testing-strategygit clone --depth 1 https://github.com/ai-debugger-inc/aidbWrote 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/ai-debugger-inc/aidb/testing-strategy)<a href="https://agentmods.dev/skills/ai-debugger-inc/aidb/testing-strategy"><img src="https://agentmods.dev/badge/skills/ai-debugger-inc/aidb/testing-strategy.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.00029 | $0.03597 |
| Opus 5 | $0.00015 | $0.01799 |
| Sonnet 5 | $0.00006 | $0.00719 |
| Haiku 4.5 | $0.00003 | $0.00360 |
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 4d 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 — 465 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIDB Testing Strategy
Priority: E2E → Integration → Unit (Highest ROI First)
CRITICAL: Test Execution Command
All tests MUST be run via ./dev-cli test run:
./dev-cli test run -s {suite} [-k 'pattern'] [-l {lang}]
- Multiple
-kand-lflags supported - NEVER use
--local- suites know their natural execution environment; forcing local causes unexpected behavior - Direct
pytestinvocation is NOT supported
This skill guides you through creating and modifying tests for the AIDB project. The test infrastructure is complete - your job is to implement tests using proven patterns.
Related Skills
When implementing tests, you may also need:
- adapter-development - Tests validate adapter behavior across languages
- mcp-tools-development - MCP tools tested with DebugInterface abstraction
- dap-protocol-guide - Tests exercise DAP protocol flows end-to-end
- ci-cd-workflows - For testing CI/CD workflows themselves (not application code)
Core Philosophy
For complete test architecture, see test infrastructure in src/tests/.
1. E2E First, Unit Last
Why E2E First?
- Validates real user workflows
- Exercises the full stack (catches integration bugs early)
- Most bugs discovered when testing actual components
- Higher ROI than unit tests initially
Testing Priority:
- E2E Tests - Complete workflows, real programs, full integration
- Integration Tests - Component interactions, adapter lifecycle, state management
- Unit Tests - Edge cases, specific logic, error handling
2. Framework Tests: Keep It Simple
Goal: Verify we can launch and debug programs using various frameworks
Pattern:
- Connect to framework app (Django, Express, Spring Boot, etc.)
- Quick smoke test: set breakpoint → inspect → step
- That's it. Don't test framework internals.
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.
- 4d ago First seen · 465 lines · 29 tokens per session scan A 3a44911c1654
testing-strategy is a skill published in the GitHub repository ai-debugger-inc/aidb (21 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 3,597 once invoked, about $0.0001 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
cover
Generate tests that do not exist yet. Analyzes coverage gaps, then writes and runs new test files across three tiers (unit, integration via testcontainers, Playwright E2E), one test-generator agent per tier, healing failures for up to 3 iterations. Use when code has no tests or when raising coverage after…
cf:test
Execute the smallest adequate verification scope and own the canonical execution proof.
scenario-testing
This skill should be used when writing tests, validating features, or needing to verify code works. Triggers on "write tests", "add test coverage", "validate feature", "integration test", "end-to-end", "e2e test", "mock", "unit test". Enforces scenario-driven testing with real dependencies in .scratch/ directory.
final-release-review
Perform pre-release planning or a final release-candidate review for openai-agents-python by comparing the target with the previous remote tag, determining the minimum compatible release type, auditing regressions and contract changes, reviewing open documentation PR coverage, drafting minor-release Key Changes, and…
implementation-strategy
Choose compatibility-aware scope for runtime and API changes in openai-agents-python. Use before initial implementation and each review-feedback batch to decide whether to patch, reset the design, preserve compatibility, or reject unsupported cases.
pr-draft-summary
Create the required PR-ready summary block, branch suggestion, title, and draft description for openai-agents-python. Use before the final response whenever the current task changed runtime code, tests, examples, build/test configuration, or docs with behavior impact, regardless of perceived change size and including…