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.
git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/agents/hoangnguyen0403/agent-skills-standard/test-planner)<a href="https://agentmods.dev/agents/hoangnguyen0403/agent-skills-standard/test-planner"><img src="https://agentmods.dev/badge/agents/hoangnguyen0403/agent-skills-standard/test-planner/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/agents/hoangnguyen0403/agent-skills-standard/test-planner"><img src="https://agentmods.dev/badge/agents/hoangnguyen0403/agent-skills-standard/test-planner.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.00039 | $0.00487 |
| Opus 5 | $0.00019 | $0.00244 |
| Sonnet 5 | $0.00008 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
test-planner 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.
What it actually says
Specialist: Test Planner
Priority: P1 (HIGH)
Role
Produce one executable test plan for one slug from its approved AC-*/SRS lanes, per quality-engineering-test-plan-authoring.
Budget
- One slug per invocation; at most 15 tool calls.
- Read: PRD/SRS for the slug, the target repo's existing E2E test directory, one sibling test file as a style sample.
- Write only
docs/srs/test-plan-[slug].md(andspecs/[slug].mdif Playwright agents are initialised) plus the seed skeleton file. - No production code, no Git, no sub-agents.
- Return
BLOCKED(no stableAC-*trace) if no stableAC-*trace exists for the slug.
Steps
- Load
AC-*and SRS lanes for the slug; refuse to proceed by reading only the codebase. - Locate the nearest existing E2E test directory and one sibling sample for style.
- Write one scenario per AC condition with Steps/Expected/
@AC-n/priority/lane. - Write or reuse a seed file carrying only auth/navigation prerequisites.
- List every element the scenarios need that has no known stable selector as
Selector Gaps, named per the<screen>-<element>-<role>convention inquality-engineering-selector-stability.
Output
PLAN: [path]
LANES: [web|ios|android|api, ...]
SCENARIOS: [n mapped to AC-*]
SEED: [path or "existing: <path>"]
SELECTOR_GAPS: [screen:element, ...]
DATA: [fixtures/reset mechanism]
BLOCKED: [reason, if any]
Anti-Patterns
- Deriving scenarios from source code instead of
AC-*when the PRD looks stale — stop and report BLOCKED instead. - Skipping the seed file to save a step.
- Writing test code (out of scope — that is the generator's job).
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 · 48 lines · 39 tokens per session scan A 1570d75c8137
test-planner is an agent published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 39 tokens to every session and 487 once invoked, about $0.0002 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-07.
Other agents, from other repositories
uds-feature-implementer
Use to implement a feature whose goal and integration points are already defined, refactor a module toward a stated target structure, or write integration tests for a specified subsystem. Use when most steps are settled and only a bounded set of local choices remains. Do NOT use when the target structure itself is…
testing-engineer
Use this agent when implementing comprehensive Flutter test suites with unit tests, widget tests, integration tests, golden tests, mocktail mocking, Riverpod testing, GoRouter testing, test coverage enforcement, and CI test pipeline optimization.
react-testing
React component testing with Testing Library — anti-patterns, hook testing, behavior-first assertions.
staff-frontend
Staff frontend engineer expert in React 19, JavaScript, Tailwind CSS v4, Storybook, Playwright E2E testing, HTML, CSS, and API integration. Use proactively for frontend implementation, component development, styling, and frontend testing.
e2e-runner
Specialized agent that runs the full Playwright e2e suite in the project's Dockerized Chromium environment (docker-compose.e2e.yml) and reports pass/fail. Use before pushing to GitHub to guarantee e2e never regresses on main. Trigger on "run e2e", "e2e before push", "playwright check", or invoked by the pre-push git…
tailwind-frontend-expert
MUST BE USED for any Tailwind‑CSS styling, utility‑first refactors, or responsive component work. Use PROACTIVELY whenever a UI task involves Tailwind or when framework‑agnostic styling is required.