Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ValorVie/custom-skillsnpx agentmods add skills/valorvie/custom-skills/testing-guideWrote 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/valorvie/custom-skills/testing-guide)<a href="https://agentmods.dev/skills/valorvie/custom-skills/testing-guide"><img src="https://agentmods.dev/badge/skills/valorvie/custom-skills/testing-guide.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.1 | $0.00081 | $0.02998 |
| Opus 5 | $0.00041 | $0.01499 |
| Sonnet 5 | $0.00016 | $0.00600 |
| Haiku 4.5 | $0.00008 | $0.00300 |
Grade A, and why
testing-guide 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 5d 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 — 363 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Guide
Language: English | 繁體中文
Version: 1.2.0 Last Updated: 2026-04-18 Applicability: Claude Code Skills
Purpose
This skill provides testing pyramid standards and best practices for systematic testing, supporting both ISTQB and Industry Pyramid frameworks.
Testing Skills Navigator | 測試技能導航
UDS provides 6 testing-related skills. Use this decision tree to find the right one:
What do you want to do? | 你想做什麼？
├── Measure code coverage (lines/branches/functions) → /coverage
├── Track which requirements have tests (AC traceability) → /ac-coverage
├── Develop with Test-Driven Development (Red-Green-Refactor) → /tdd
├── Write BDD scenarios (Given-When-Then) → /bdd
├── Define acceptance tests with stakeholders → /atdd
└── Learn testing standards and best practices → /testing (this skill)
| Skill | Focus | 焦點 |
|---|---|---|
/testing |
Standards and best practices reference | 測試標準與最佳實踐參考 |
/coverage |
Code-level coverage analysis | 程式碼層級覆蓋率分析 |
/ac-coverage |
Requirement-level AC traceability | 需求層級 AC 可追蹤性 |
/tdd |
Red-Green-Refactor development cycle | 紅-綠-重構開發循環 |
/bdd |
Behavior scenarios with Given-When-Then | Given-When-Then 行為場景 |
/atdd |
Acceptance criteria with stakeholders | 與利害關係人定義驗收條件 |
Framework Selection
| Framework | Levels | Best For |
|---|---|---|
| ISTQB | UT → IT/SIT → ST → AT/UAT | Enterprise, compliance, formal QA |
| Industry Pyramid | UT (70%) → IT (20%) → E2E (10%) | Agile, DevOps, CI/CD |
Note on Integration Testing abbreviation:
- IT (Integration Testing): Agile/DevOps communities
- SIT (System Integration Testing): Enterprise/ISTQB contexts
- Both refer to the same testing level
Quick Reference
Testing Pyramid (Industry Standard)
┌─────────┐
│ E2E │ ← 10% (Fewer, slower)
─┴─────────┴─
┌─────────────┐
│ IT/SIT │ ← 20% (Integration)
─┴─────────────┴─
┌─────────────────┐
│ UT │ ← 70% (Unit)
└─────────────────┘
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.
- 5d ago First seen · 363 lines · 81 tokens per session scan A f8375ac23ab4
testing-guide is a skill published in the GitHub repository ValorVie/custom-skills (5 stars, last pushed 8d ago), licensed MIT. It adds 81 tokens to every session and 2,998 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
accessibility-testing
Skill "accessibility-testing" from vibeeval/vibecosystem, covering accessibility testing, axe-core setup, jest-axe (unit / component tests), playwright-axe (e2e) and cypress-axe.
testing-strategy
Follow the testing pyramid — more unit tests, fewer integration tests, even fewer e2e tests.
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.
vc:web-testing
Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
javascript-testing-patterns
Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.
webapp-testing-jp
A Japanese-language guide to testing web applications, including unit, integration, and end-to-end tests. End-to-end tests check a complete user flow through the application.