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/be-changerequestnpx skills add hiepdnh/Agentic-Development-Lifecycle --skill be-changerequestgit 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/be-changerequest)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/be-changerequest"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/be-changerequest.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.00098 | $0.01472 |
| Opus 5 | $0.00049 | $0.00736 |
| Sonnet 5 | $0.00020 | $0.00294 |
| Haiku 4.5 | $0.00010 | $0.00147 |
Grade A, and why
be-changerequest 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 4d 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: /be-changerequest
Role: Bridge Engineer / PM
Mục đích: Xử lý yêu cầu thay đổi từ khách JP một cách có kiểm soát — impact analysis rõ ràng, approval trail đầy đủ, không merge thay đổi ngầm vào spec.
Context
Thay đổi spec sau sign-off là rủi ro cao nhất trong JP outsource:
- Khách JP hay yêu cầu thay đổi nhỏ qua email/chat mà không có formal CR
- Dev VN implement "cho nhanh" mà không có approval trail → sau này khách chất vấn
- Impact chưa được estimate → scope creep không kiểm soát được
Nguyên tắc: Mọi thay đổi sau sign-off đều phải có CR document trước khi dev touch code.
Hướng dẫn thực hiện
Bước 0 — Load glossary
Đọc templates/jp-vn-en-glossary.md trước khi xử lý thuật ngữ kỹ thuật.
Bước 1 — Gate: Thu thập thông tin CR
Dùng AskUserQuestion tool:
- Nguồn yêu cầu: Email từ JP / Meeting / Slack/Teams / Formal 変更依頼書
- Loại thay đổi: Thêm feature mới / Sửa spec hiện tại / Bỏ scope / Performance requirement mới / UI/UX adjustment
- Urgency: Cần trong sprint hiện tại / Sprint sau / Flexible
Chờ confirm.
Bước 2 — Phân tích Impact
Đọc:
docs/tasks/[TASK-ID]/requirements.md— spec gốc đang bị thay đổidocs/tasks/[TASK-ID]/analysis.md— implementation đã plan hoặc đang làmdocs/decisions/ADR-*.md— quyết định kỹ thuật liên quan
Phân tích theo 4 chiều:
## Impact Analysis: CR-[NUMBER]
### Scope Impact
- Files/modules bị ảnh hưởng: [list]
- ACs bị thay đổi / thêm / bỏ: [diff so với spec gốc]
- Test cases cần cập nhật: [list]
### Effort Impact
- Estimate thêm: [X man-hours / man-days]
- Có thể làm trong sprint hiện tại: [Yes / No / Partial]
- Nếu No: cần push sang sprint [N+1 / TBD]
### Risk Impact
- Risk mới: [list]
- Dependencies bị ảnh hưởng: [list]
- Regression risk: [Low / Medium / High]
### Schedule Impact
- Deadline hiện tại: [Date]
- Impact đến deadline: [None / Trễ X ngày / Cần thương lượng lại]
Bước 3 — Gate: Xác nhận impact trước khi soạn CR
## Tôi đã phân tích impact của yêu cầu thay đổi.
[Hiển thị impact analysis từ Bước 2]
| # | Câu hỏi | Lựa chọn |
|---|---------|---------|
| 1 | Impact analysis có chính xác không? | A: Chính xác / B: Cần điều chỉnh: ___ / C: Khác: ___ |
| 2 | Ai là người approve CR phía team? | _(điền tên PM / Tech Lead)_ |
| 3 | Cần gửi estimate cho JP trước khi approve không? | A: Có — gửi email estimate trước / B: Không — tiếp tục tạo CR doc / 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.
- 4d ago First seen · 147 lines · 98 tokens per session scan A b6e178a5e04a
be-changerequest is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 7d ago), licensed MIT. It adds 98 tokens to every session and 1,472 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
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
project-init
Scaffold an unconfigured directory into a configured pi project. Interactive, profile-driven: previews the planned writes, then writes AGENTS.md, .pi/settings.json and prompt files — optionally also a knowledge base, an openspec/ scaffold, and user-global /.pi/agent/settings.json. Use on a bare directory, or when the…