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/dev-implementnpx skills add hiepdnh/Agentic-Development-Lifecycle --skill dev-implementgit clone --depth 1 https://github.com/hiepdnh/Agentic-Development-LifecycleWhat 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.00068 | $0.01900 |
| Opus 5 | $0.00034 | $0.00950 |
| Sonnet 5 | $0.00014 | $0.00380 |
| Haiku 4.5 | $0.00007 | $0.00190 |
Grade A, and why
dev-implement 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 2d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: /dev-implement
Role: Developer
Mục đích: Implement code sau khi phương án đã chọn từ /dev-analyze. File-by-file với gate sau mỗi file.
Quan trọng: Chạy /dev-analyze trước
Skill này yêu cầu docs/tasks/[TASK-ID]/analysis.md đã tồn tại.
Nếu chưa có → chạy /dev-analyze trước.
Cách spawn subagent
Dùng Agent tool để spawn subagent. Mỗi subagent nhận context tối thiểu cần thiết — không pass full conversation history.
Hướng dẫn thực hiện
Bước 1 — Đọc analysis doc
Đọc docs/tasks/[TASK-ID]/analysis.md:
- Phương án đã chọn
- Danh sách files cần thay đổi
- Quyết định kỹ thuật đã confirm
Bước 1b — Gate: TDD Lane (opt-in)
Trước khi implement, hỏi:
## Mode implement
| | Lựa chọn |
|---|---------|
| A | Standard — implement code trước, test sau (mặc định) |
| B | TDD — viết test trước, code sau (recommend cho business logic phức tạp) |
Nếu chọn TDD (B):
- Với mỗi file business logic: viết test (failing) trước
- Gate: confirm test cases cover đủ ACs
- Implement code cho test pass
- Báo cáo: "Tests: N passing / M failing" sau mỗi file
Nếu chọn Standard (A): tiếp tục bình thường.
Chờ confirm.
Bước 2 — Gate: Xác nhận implementation plan
## Tôi sẽ implement [TASK-ID] theo Phương án [X].
**Files cần thay đổi** (theo thứ tự):
1. `[file 1]` — [create/modify/delete] — [lý do]
2. `[file 2]` — [create/modify/delete] — [lý do]
**Thứ tự implement**: [giải thích tại sao thứ tự này — dependencies]
**Setup trước khi code**:
- Branch: `feature/[TASK-ID]-[slug]`
- DB migration cần tạo: [yes/no]
- ENV variables mới: [list hoặc "none"]
| | Lựa chọn |
|---|---------|
| A | Bắt đầu với `[file 1]` ngay |
| B | Điều chỉnh thứ tự — thứ tự mới: ___ |
| C | Khác: ___ |
Chờ confirm.
Bước 3 — Implement từng file
Với mỗi file, theo thứ tự:
- Đọc file hiện tại (nếu modify)
- Implement thay đổi
- Report ngắn
Template báo cáo sau mỗi file:
## File [N/Total]: `[path]` ✅
**Thay đổi**:
- [Mô tả thay đổi 1]
- [Mô tả thay đổi 2]
**Tests**: [Viết inline / Cần viết riêng / N/A]
| | Lựa chọn |
|---|---------|
| A | Tiếp tục `[file tiếp theo]` |
| B | Dừng lại — cần điều chỉnh: ___ |
| 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.
- 2d ago First seen · 233 lines · 68 tokens per session scan A 2e9e89434abe
dev-implement is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 5d ago), licensed MIT. It adds 68 tokens to every session and 1,900 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.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.