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 Xiaowen-Jiang/agent-enterprise --skill testing_strategygit clone --depth 1 https://github.com/Xiaowen-Jiang/agent-enterpriseWrote 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/xiaowen-jiang/agent-enterprise/testing_strategy)<a href="https://agentmods.dev/skills/xiaowen-jiang/agent-enterprise/testing_strategy"><img src="https://agentmods.dev/badge/skills/xiaowen-jiang/agent-enterprise/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/xiaowen-jiang/agent-enterprise/testing_strategy"><img src="https://agentmods.dev/badge/skills/xiaowen-jiang/agent-enterprise/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.00018 | $0.00373 |
| Opus 5.5 | $0.00007 | $0.00149 |
| Sonnet 5.5 | $0.00004 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00037 |
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.
What it actually says
Process
- Read the code under test — Understand inputs, outputs, and side effects
- Identify test boundaries — What is a unit? What needs integration testing?
- Map test cases — Happy path, edge cases, error cases, boundary values
- Write unit tests — Isolated, fast, mock external dependencies
- Write integration tests — Test component interactions with real dependencies
- Consider E2E scenarios — Full user flows that validate the system end-to-end
- Prioritize — Critical paths first, then edge cases
Output Format
Provide a test matrix:
| Test Name | Type | Input | Expected Output | Priority |
|---|---|---|---|---|
| test_create_user_success | unit | valid user data | user object returned | P0 |
| test_create_user_duplicate_email | unit | existing email | 409 error | P0 |
| test_user_flow_signup_to_order | e2e | full flow | order created | P1 |
Then provide the actual test code.
Guidelines
- Test behavior, not implementation details
- One assertion per test (or closely related assertions)
- Use descriptive test names that explain the scenario
- Arrange-Act-Assert pattern
- No test interdependencies — each test should be independent
- Mock at boundaries (database, external APIs), not internal functions
- Cover both success and failure paths
- Include edge cases: empty inputs, max values, unicode, concurrent access
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 · 42 lines · 18 tokens per session scan A b0ec4af6f52d
Testing Strategy is a skill published in the GitHub repository Xiaowen-Jiang/agent-enterprise (52 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 373 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
proof-strategy
Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".
proof-recon
Testing reconnaissance — inventory all tests, frameworks, coverage, CI integration, and assess testing maturity for project takeover. Use when asked to "understand the tests", "testing assessment", "what's tested", or "test inventory".
ios-test
XCTest patterns for unit tests, UI tests, and SwiftData testing with in-memory containers under Swift 6 strict concurrency, plus test performance budgets. Use when writing or fixing tests, setting up test targets, testing SwiftData models, or planning CI test suites. Trigger on "write a test", "unit test", "XCTest"…
testing-strategy
Write comprehensive test suites with proper structure, mocking strategies, fixtures, and coverage goals. Use when implementing unit tests, integration tests, or e2e tests. Triggers on: tests, testing, unit test, integration test, e2e, jest, vitest, pytest, mocking, TDD.
tsq-testing
A guide to planning and writing software tests, including unit tests, integration tests, end-to-end tests, test coverage, and the Given-When-Then format. TDD means writing a failing test, making it pass with the smallest change, then cleaning up the code.
test-generation
Generate a test strategy and starter test stubs for given modules across unit, integration, and e2e layers (pytest/jest/playwright). Trigger on: generate tests, test plan, test strategy, coverage plan, test scaffolding.