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-utnpx skills add hiepdnh/Agentic-Development-Lifecycle --skill qa-utgit 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-ut)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/qa-ut"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/qa-ut.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.00097 | $0.01304 |
| Opus 5 | $0.00048 | $0.00652 |
| Sonnet 5 | $0.00019 | $0.00261 |
| Haiku 4.5 | $0.00010 | $0.00130 |
Grade A, and why
qa-ut 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: /qa-ut
Role: QA Engineer
Mục đích: Tạo Unit Test plan cho từng function/component, hỗ trợ thực thi và ghi kết quả. Khi fail → bug feedback loop rõ ràng về dev phase.
Hướng dẫn thực hiện
Bước 1 — Đọc input
Đọc theo thứ tự:
docs/tasks/[TASK-ID]/requirements.md— AC list, business rulesdocs/tasks/[TASK-ID]/analysis.md— files đã implement, approach đã chọn- Màn hình / API docs liên quan (nếu có trong analysis.md)
Bước 2 — Gate: Xác nhận scope UT
Dùng AskUserQuestion tool:
- Component/Function: Những unit nào cần test? (Nếu không rõ → AI tự suy ra từ analysis.md)
- Test framework: Jest / JUnit / pytest / Vitest / khác?
- Coverage target: Line coverage target % nếu có requirement
- Mock strategy: Unit test thuần (mock all deps) hay lean integration (mock chỉ external)?
Chờ confirm.
Bước 3 — Tạo UT Plan
Tạo docs/tasks/[TASK-ID]/test-plan-ut.md dùng template templates/test-plan.md với các TC:
Mỗi TC có:
- TC-UT-XXX: ID dạng
TC-UT-001 - Unit: Tên function/method/component đang test
- Input: Dữ liệu đầu vào cụ thể
- Expected: Output/behavior mong đợi
- Assertion: Assertion cụ thể (ví dụ:
expect(result).toBe(42)) - Type: Happy / Edge / Negative / Error
Cover đầy đủ:
- Happy path (input hợp lệ, output đúng)
- Edge cases (boundary values, empty, null, zero)
- Negative cases (invalid input, type mismatch)
- Error cases (exception thrown, error message)
Bước 3.5 — Render HTML checklist
Sinh docs/tasks/[TASK-ID]/test-plan-ut.html với:
- Checklist tick từng TC, state lưu localStorage (key:
ut-[TASK-ID]) - Group theo Unit (function/component) dùng
<details><summary> - Filter theo Type (Happy / Edge / Negative / Error)
- Pill màu theo priority: High=🔴, Med=🟡, Low=🟢
File HTML KHÔNG commit. test-plan-ut.md là source of truth.
✓ Đã sinh `docs/tasks/[TASK-ID]/test-plan-ut.html`
Mở bằng browser khi chạy test để tick từng TC.
Bước 4 — Gate: Validate test plan
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 · 147 lines · 97 tokens per session scan A ee67df4ceaa6
qa-ut is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 8d ago), licensed MIT. It adds 97 tokens to every session and 1,304 once invoked, about $0.0005 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
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
nunit-testing
Use when writing or modifying tests in NUnit's own test projects, or when making a behavioral change to production code that needs test coverage. Covers test structure, attribute choice, helper visibility, platform guards, and which test projects are real.
detect-flaky-tests
Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM lanes). For each newly-detected flaky test or infra issue, opens a GitHub issue with full evidence and a draft fix PR. Does…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
add-go-test
Write or extend Go unit tests in this repo. Use when the user asks to add or update Go tests.