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 HoangNguyen0403/agent-skills-standard --skill quality-engineering-test-plan-authoringgit 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/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-test-plan-authoring)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-test-plan-authoring"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-test-plan-authoring/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/hoangnguyen0403/agent-skills-standard/quality-engineering-test-plan-authoring"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-test-plan-authoring.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.00045 | $0.00569 |
| Opus 5 | $0.00023 | $0.00284 |
| Sonnet 5 | $0.00009 | $0.00114 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
quality-engineering-test-plan-authoring 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
Quality Engineering: Test Plan Authoring
Priority: P1 (HIGH)
Input
AC-* IDs and SRS lanes (unit/integration/E2E-web/E2E-mobile/API) from the
approved PRD/SRS. Never derive scenarios from reading the code — code shows
what exists, not what the acceptance criteria require.
Output
docs/srs/test-plan-[slug].md (and specs/[slug].md once Playwright Test
Agents are initialised on the target repo). Each scenario block: Steps,
Expected, @AC-n tag, priority, exactly one lane (web|ios|android|api).
One scenario covers one AC condition — do not fold multiple conditions into
one scenario.
Seed
tests/seed.spec.ts (or platform equivalent) carries only shared
prerequisites: auth and navigation to the starting screen. No assertions.
Mandatory Sections
Selector Gaps (elements the plan needs that have no stable id yet — feeds
specialist-testid-inserter, Phase P1, not yet implemented) and Data & Reset
(fixtures needed, how state resets between scenarios). Gaps must follow the
<screen>-<element>-<role> naming convention defined in
quality-engineering-selector-stability.
Relationship to Zephyr
Manual Zephyr TCs stay the system of record for business sign-off
(quality-engineering-zephyr-test-generation); this skill's scenarios carry
a bidirectional TC-key reference where one exists, and are additive, not a
replacement.
Anti-Patterns
- A scenario without an
Expectedoutcome. - A plan derived from source code instead of
AC-*. - Duplicating unit-level coverage in an E2E scenario.
- A scenario spanning more than one
lane. - A plan with no seed reference.
References
What ships with it
4 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 · 69 lines · 45 tokens per session scan A 08322b2b92d4
quality-engineering-test-plan-authoring is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 569 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 skills, from other repositories
verify
Build/launch/drive recipe for verifying apps/docs changes at runtime (demos, docs pages, llms.txt).
testing-guide
A testing guide covering the test pyramid and standards for unit, integration, system, and end-to-end tests.
patrol-e2e-testing
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
flutter-mcp-cli-runtime-validation
Run Flutter MCP runtime validation from CLI in two steps (launch app, then run validate-runtime), including toolkit-extension gating, screenshot/layout capture, app error collection, optional reload verification, and retry handling for transient first-connect failures.
test-mcp-server
Use when testing MCP servers -- e2e tests with the sunpeak inspector, visual regression testing, live testing against real ChatGPT, multi-model evals, Playwright configuration, or scaffolding test infrastructure with "sunpeak test init". Works with any MCP server (Python, Go, TypeScript, etc.), not just sunpeak…