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 agentmods add skills/hiepdnh/agentic-development-lifecycle/qa-testplannpx skills add hiepdnh/Agentic-Development-Lifecycle --skill qa-testplangit clone --depth 1 https://github.com/hiepdnh/Agentic-Development-LifecycleWrote 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/hiepdnh/agentic-development-lifecycle/qa-testplan)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/qa-testplan"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/qa-testplan.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 | $0.00075 | $0.01009 |
| Opus 5 | $0.00037 | $0.00504 |
| Sonnet 5 | $0.00015 | $0.00202 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade A, and why
qa-testplan 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: /qa-testplan
Role: QA Engineer
Mục đích: Tạo test plan toàn diện từ spec/user stories, bao gồm test cases và strategy.
Hướng dẫn thực hiện
Bước 1 — Đọc input
Đọc docs/tasks/[TASK-ID]/requirements.md và màn hình/API docs liên quan.
Bước 2 — Gate: Xác nhận scope test
## Tôi sẽ tạo test plan cho: [Feature name]
Tôi đọc spec và xác định:
- [N] Acceptance Criteria cần verify
- [M] Business Rules cần test
- Màn hình liên quan: [list]
- API liên quan: [list]
Trước khi soạn test plan, tôi cần hỏi:
| # | Câu hỏi | Lựa chọn |
|---|---------|---------|
| 1 | Test level cần cover? | A: Unit / B: Integration / C: E2E / D: Performance / E: Security / F: Tất cả / G: Khác: ___ |
| 2 | Môi trường test? | A: Dev / B: Staging / C: Prod-like / D: Khác: ___ |
| 3 | Có dữ liệu test đặc biệt cần chuẩn bị không? | A: Không / B: Có — loại data: ___ / C: Khác: ___ |
| 4 | Regression scope — những gì cần retest? | _(liệt kê features/flows cần retest)_ |
Chờ confirm.
Bước 3 — Tạo Test Plan
Tạo docs/tasks/[TASK-ID]/test-plan.md sử dụng template templates/test-plan.md.
Bước 3.5 — Render HTML companion (interactive checklist)
Sinh docs/tasks/[TASK-ID]/test-plan.html từ template templates/html-artifact.html:
- Inject
<ul class="checklist" data-storage-key="testplan-[TASK-ID]">cho từng TC - Mỗi
<li>có<input type="checkbox" data-id="TC-XXX">+ label = TC name - Group theo type: Happy / Edge / Negative dùng
<details><summary>mở rộng - Header có
<input type="search" data-filter="...">để filter TC theo từ khoá - Pill
pill-ok|warn|errcho priority High/Med/Low
QA tick checkbox khi chạy test, state lưu localStorage — không cần copy vào Markdown.
File HTML KHÔNG commit (đã có .gitignore). test-plan.md vẫn là source of truth commit vào repo.
✓ Đã sinh `docs/tasks/[TASK-ID]/test-plan.html`
Mở bằng browser khi chạy test để tick checklist (state lưu localStorage).
Bước 4 — Gate cuối
Test plan đã soạn xong với [N] test cases.
| # | Câu hỏi | Lựa chọn |
|---|---------|---------|
| 1 | Test case nào có vẻ thiếu? | A: Không thiếu / B: Thiếu — mô tả: ___ / C: Khác: ___ |
| 2 | Có edge case domain đặc thù tôi chưa cover? | A: Không / B: Có — edge case: ___ / C: Khác: ___ |
| 3 | Exit criteria có đủ chặt không? | A: Đủ rồi / B: Cần thêm điều kiện: ___ / C: Khác: ___ |
| 4 | Muốn tôi generate code test tự động từ test plan không? | A: Có / B: Không — sẽ viết tay / C: Khác: ___ |
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.
- 5d ago First seen · 90 lines · 75 tokens per session scan A 3eadafc19644
qa-testplan is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 8d ago), licensed MIT. It adds 75 tokens to every session and 1,009 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…