Borrowing it
Nothing to install: this file belongs to hoangsonww/PetSwipe-Match-App. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hoangsonww/PetSwipe-Match-App/master/.agents/skills/testing-and-validation/SKILL.mdgit clone --depth 1 https://github.com/hoangsonww/PetSwipe-Match-AppWrote 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/hoangsonww/petswipe-match-app/testing-and-validation)<a href="https://agentmods.dev/skills/hoangsonww/petswipe-match-app/testing-and-validation"><img src="https://agentmods.dev/badge/skills/hoangsonww/petswipe-match-app/testing-and-validation/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/hoangsonww/petswipe-match-app/testing-and-validation"><img src="https://agentmods.dev/badge/skills/hoangsonww/petswipe-match-app/testing-and-validation.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.00052 | $0.00218 |
| Opus 5 | $0.00026 | $0.00109 |
| Sonnet 5 | $0.00010 | $0.00044 |
| Haiku 4.5 | $0.00005 | $0.00022 |
Grade A, and why
testing-and-validation 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 9d 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
Use this skill when validation strategy matters as much as the code change.
Workflow
- Identify the touched area and its real blast radius.
- Choose the smallest reliable checks that validate that area.
- Prefer targeted checks before broad repo-wide checks.
- Report clearly what each command validates.
- Separate new failures from pre-existing repo debt.
PetSwipe Guidance
- Frontend: prefer targeted
npx eslintover broad linting when possible. - Backend: prefer
npm run buildplus targeted tests. - Infra: prefer render and preflight commands.
- Docs: validate by re-reading commands, paths, and claims against the repo.
If needed, spawn test_guard to recommend the validation set before editing.
Read references/validation-playbook.md.
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.
- 9d ago First seen · 26 lines · 52 tokens per session scan A 1a09e008c630
testing-and-validation is a skill published in the GitHub repository hoangsonww/PetSwipe-Match-App (24 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 218 once invoked, about $0.0003 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
prowler-test-sdk
Testing patterns for Prowler SDK (Python). Trigger: When writing tests for the Prowler SDK (checks/services/providers), including provider-specific mocking rules (moto for AWS only).
playwright
Playwright E2E testing patterns. Trigger: When writing Playwright E2E tests (Page Object Model, selectors, MCP exploration workflow). For Prowler-specific UI conventions under ui/tests, also use prowler-test-ui.
prowler-test-ui
E2E testing patterns for Prowler UI (Playwright). Trigger: When writing Playwright E2E tests under ui/tests in the Prowler UI (Prowler-specific base page/helpers, tags, flows).
tdd
Test-Driven Development workflow for ALL Prowler components (UI, SDK, API). Trigger: ALWAYS when implementing features, fixing bugs, or refactoring - regardless of component. This is a MANDATORY workflow, not optional.
prowler-test-api
Testing patterns for Prowler API: JSON:API, Celery tasks, RLS isolation, RBAC. Trigger: When writing tests for api/ (JSON:API requests/assertions, cross-tenant isolation, RBAC, Celery tasks, viewsets/serializers).
prowler-test-mcp
Testing patterns for the Prowler MCP Server: in-memory FastMCP clients, the ProwlerAPIClient singleton, JSON:API model builders and mocked httpx transports. Trigger: When writing tests under mcpserver/tests/ (tools, models, apiclient, auth, sub-servers).