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-regressionnpx skills add hiepdnh/Agentic-Development-Lifecycle --skill qa-regressiongit 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-regression)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/qa-regression"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/qa-regression.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.00064 | $0.01292 |
| Opus 5 | $0.00032 | $0.00646 |
| Sonnet 5 | $0.00013 | $0.00258 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
qa-regression 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: /qa-regression
Role: QA Engineer
Mục đích: Tạo regression test checklist trước release. Verify tính năng cũ không bị ảnh hưởng bởi changes mới.
Khi nào dùng
- Trước mỗi release / sprint end
- Sau merge PR có changes ảnh hưởng shared code (auth, middleware, DB migration)
- Khi PM yêu cầu sign-off trước khi deploy production
Hướng dẫn thực hiện
Bước 1 — Thu thập scope changes
Spawn subagent (dùng Agent tool) để đọc:
git log [base]..HEAD --name-only— files đã thay đổidocs/tasks/[TASK-IDs]/requirements.md— tất cả tasks trong release
Subagent trả về: file list + blast radius analysis.
Bước 2 — Gate: Xác nhận regression scope
## Regression scope cho release [version/sprint]:
**Tasks trong release**: [list TASK-IDs]
**Files thay đổi**: [N files]
**Blast radius analysis**:
| Area | Risk | Lý do |
|------|------|-------|
| [Auth flow] | High | auth.service.js modified |
| [Payment] | Low | Không có changes liên quan |
| [Dashboard] | Medium | Shared component updated |
**Đề xuất test priority**:
- 🔴 Must Test: [list areas]
- 🟡 Should Test: [list areas]
- 🟢 Smoke only: [list areas — nếu thiếu thời gian, skip được]
| | Lựa chọn |
|---|---------|
| A | Confirm — tạo checklist theo scope này |
| B | Điều chỉnh scope — sửa: ___ |
| C | Khác: ___ |
Chờ confirm.
Bước 3 — Tạo Regression Checklist (HTML là format chính)
Regression checklist là one-shot decision artifact (chạy → tick → go/no-go) — format chính là HTML, không cần Markdown commit. Sinh docs/tasks/regression-[sprint-or-version].html từ template templates/html-artifact.html:
- 3 sections collapse
<details>cho 🔴 Must Test / 🟡 Should Test / 🟢 Smoke - Mỗi section là
<table data-sortable>với cột: ID | Test Case | Steps | Expected | Result | Bug? - Cột Result có
<select>(Pass/Fail/Blocked) cập nhật vàodata-state, đổi background row theo state - Header có Go/No-Go badge tự động: chuyển đỏ nếu bất kỳ Must Test = Fail
- Toolbar có button "Export results" — copy bảng về Markdown để paste vào sprint report
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 · 159 lines · 64 tokens per session scan A 87c80c09f184
qa-regression is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 8d ago), licensed MIT. It adds 64 tokens to every session and 1,292 once invoked, about $0.0003 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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…