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-itnpx skills add hiepdnh/Agentic-Development-Lifecycle --skill qa-itgit 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-it)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/qa-it"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/qa-it.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.00099 | $0.01415 |
| Opus 5 | $0.00049 | $0.00707 |
| Sonnet 5 | $0.00020 | $0.00283 |
| Haiku 4.5 | $0.00010 | $0.00142 |
Grade A, and why
qa-it 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: /qa-it
Role: QA Engineer
Mục đích: Tạo Integration/E2E Test plan cover luồng nghiệp vụ end-to-end. Chỉ chạy SAU KHI UT passed. Khi fail → bug feedback loop về dev phase.
Hướng dẫn thực hiện
Bước 0 — Kiểm tra UT prerequisite
Đọc docs/tasks/[TASK-ID]/ut-results.md.
-
Nếu không tồn tại hoặc verdict ≠
PASS:⚠️ IT không thể chạy khi UT chưa pass. Chạy /qa-ut trước, sau đó quay lại /qa-it.Dừng tại đây.
-
Nếu verdict =
PASS→ tiếp tục Bước 1.
Bước 1 — Đọc input
Đọc theo thứ tự:
docs/tasks/[TASK-ID]/requirements.md— luồng nghiệp vụ, AC end-to-enddocs/tasks/[TASK-ID]/analysis.md— phương án đã chọn, API/Screen affecteddocs/tasks/[TASK-ID]/test-plan-ut.md— scope đã test ở UT, tránh duplicate- Screen/API docs liên quan (nếu có
## Screen Design Stubhoặc## API Design Stubtrong analysis.md)
Bước 2 — Gate: Xác nhận scope IT
Dùng AskUserQuestion tool:
- Integration flows: Luồng nào cần test end-to-end? (Ví dụ: Đăng nhập → Tạo đơn → Thanh toán)
- Environment: Staging / Dev / Prod-like?
- Test data: Data đặc biệt cần setup? (user accounts, seed data, mock services)
- External dependencies: API bên thứ 3 cần mock hay dùng thật?
Chờ confirm.
Bước 3 — Tạo IT Plan
Tạo docs/tasks/[TASK-ID]/test-plan-it.md dùng template templates/test-plan.md với các TC:
Mỗi TC có:
- TC-IT-XXX: ID dạng
TC-IT-001 - Flow: Tên luồng nghiệp vụ end-to-end
- Preconditions: Data/state cần setup trước khi test
- Steps: Các bước thực thi có thứ tự (numbered)
- Expected Result: Kết quả mong đợi sau mỗi step quan trọng
- Postconditions: State của hệ thống sau khi test hoàn thành
- Type: Happy / Edge / Error / Performance
Cover đầy đủ:
- Happy flow (luồng chính hoàn chỉnh từ đầu đến cuối)
- Cross-component integration (API ↔ DB ↔ Cache, Screen ↔ API)
- Error recovery (service timeout, network failure, rollback)
- Data integrity (không mất data khi fail giữa chừng)
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 · 152 lines · 99 tokens per session scan A e4495dab7b19
qa-it is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 8d ago), licensed MIT. It adds 99 tokens to every session and 1,415 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
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
__SKILL_ID__
This fixture verifies that skill content can be written into the target sandbox and queried back immediately.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…