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-bugnpx skills add hiepdnh/Agentic-Development-Lifecycle --skill qa-buggit 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-bug)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/qa-bug"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/qa-bug.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.00071 | $0.00626 |
| Opus 5 | $0.00036 | $0.00313 |
| Sonnet 5 | $0.00014 | $0.00125 |
| Haiku 4.5 | $0.00007 | $0.00063 |
Grade A, and why
qa-bug 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 3d 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
Skill: /qa-bug
Role: QA Engineer
Mục đích: Tạo bug report chuẩn, đủ thông tin để dev reproduce và fix.
Hướng dẫn thực hiện
Bước 1 — Gate: Thu thập thông tin
## Tôi sẽ giúp bạn soạn bug report.
Cho tôi biết:
| # | Câu hỏi | Lựa chọn |
|---|---------|---------|
| 1 | Mô tả ngắn gọn lỗi xảy ra | _(điền vào)_ |
| 2 | Môi trường phát hiện | A: Dev / B: Staging / C: Production / D: Khác: ___ |
| 3 | Browser / OS / device | _(điền vào)_ |
| 4 | Steps to reproduce | _(điền vào — dù rough cũng được)_ |
| 5 | Expected vs Actual behavior | _(điền vào)_ |
| 6 | Có screenshot/log không? | A: Có (đính kèm) / B: Không / C: Khác: ___ |
| 7 | Tần suất lỗi | A: 100% mỗi lần reproduce / B: Intermittent (~___%) / C: Khác: ___ |
Bước 2 — Phân loại severity
Đánh giá dựa trên impact:
- Critical: Crash, data loss, security breach, payment failure
- High: Core feature broken, no workaround
- Medium: Feature degraded, workaround exists
- Low: UI issue, minor inconvenience
Hỏi nếu chưa rõ: "Lỗi này có workaround không? User có thể tiếp tục công việc không?"
Bước 3 — Tạo Bug Report
Tạo bug report sử dụng template templates/bug-report.md.
Bước 4 — Gate cuối
Bug report đã soạn xong.
Trước khi submit:
| # | Câu hỏi | Lựa chọn |
|---|---------|---------|
| 1 | Steps to reproduce — confirm reproduce được không? | A: Có / B: Không — sửa steps: ___ / C: Khác: ___ |
| 2 | Severity [X] có đúng không? | A: Đúng / B: Cao hơn — lên: ___ / C: Thấp hơn — xuống: ___ / D: Khác: ___ |
| 3 | Cần tag thêm người nào không? | A: Không / B: Có — username: ___ / C: Khác: ___ |
Chờ confirm.
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.
- 3d ago First seen · 65 lines · 71 tokens per session scan A ec456dc0a8d4
qa-bug is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 6d ago), licensed MIT. It adds 71 tokens to every session and 626 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…