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 irahardianto/awesome-agv --skill testing-strategygit clone --depth 1 https://github.com/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/testing-strategy)<a href="https://agentmods.dev/skills/irahardianto/awesome-agv/testing-strategy"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/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/irahardianto/awesome-agv/testing-strategy"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/testing-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00067 | $0.01026 |
| Opus 5.5 | $0.00027 | $0.00410 |
| Sonnet 5.5 | $0.00013 | $0.00205 |
| Haiku 4.5 | $0.00007 | $0.00103 |
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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Strategy Skill
This skill provides detailed implementation guidance for testing. The core mandates
(TDD, AAA, test pyramid ratios) are in the testing-strategy rule and are always active.
Load this skill when you need specific patterns, tools, or language conventions.
Test Doubles Strategy
Unit Tests: Use mocks/stubs for all driven ports
- Mock repositories return pre-defined data
- Mock external APIs return successful responses
- Mock time/random for deterministic tests
- Control test environment completely
Integration Tests: Use real infrastructure
- Testcontainers spins up PostgreSQL, Redis, message queues
- Firebase emulator spins up Firebase Authentication, Cloud Firestore, Realtime Database, Cloud Storage for Firebase, Firebase Hosting, Cloud Functions, Pub/Sub, and Firebase Extensions
- Test actual database queries, connection handling, transactions
- Verify adapter implementations work with real services
Best Practice: Generate at least 2 implementations per driven port:
- Production adapter (PostgreSQL, GCP GCS, etc.)
- Test adapter (in-memory, fake implementation)
Test Organization
Co-located Tests (Unit & Integration)
Place tests next to the file they test. This keeps tests visible, encourages maintenance, and supports refactoring.
Naming Conventions by Language:
| Language | Unit | Integration |
|---|---|---|
| TS/JS | framework-dependent — see note below | framework-dependent |
| Go | *_test.go |
*_integration_test.go |
| Dart/Flutter | *_test.dart (in test/ mirroring lib/) |
*_integration_test.dart |
| Python | test_*.py |
test_*_integration.py |
| Java | *Test.java |
*IT.java |
| Rust | #[cfg(test)] mod tests inline |
tests/ at crate root |
TS/JS test-naming is framework-dependent, not a single suffix. Authoritative rule:
@.agents/skills/typescript-idioms/references/project-structure.md§Test Organization. Summary: Vue & Angular use*.spec.ts(CLI default); React uses*.test.tsx; generic TS, Hono, and Next.js App Router use*.test.ts(Next.js co-locates in__tests__/). Do not mixtestandspecsuffixes within a single package — follow that package's framework convention.
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 · 94 lines · 67 tokens per session scan A 11f9353d4a64
testing-strategy is a skill published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 12d ago), licensed MIT. It adds 67 tokens to every session and 1,026 once invoked, about $0.0003 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
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
flutter-bloc-state-management
Implement BLoC/Cubit state, events, transitions, and async concurrency in Flutter. Use for BLoC/Cubit feature logic, debounced/cancellable events, state rendering, or bloc tests—not generic widget-only work.
angular-testing
Write Angular component tests using TestBed, ComponentHarness, and HttpTestingController with proper signal input handling. Use when writing component tests, mocking HTTP calls, or testing signal inputs.
mlops-validation
Add the validation layers that gate a merge — ty typing, Ruff linting, pytest coverage, structured logging, and the trivy, pip-audit, and gitleaks scans. Use when hardening code quality or wiring the mise run check task.
testing-guide
A testing guide covering the test pyramid and standards for unit, integration, system, and end-to-end tests.
testing
Testing strategies and methodologies including TDD and E2E testing. Use when writing tests, implementing TDD workflow, or setting up E2E test infrastructure.