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-reviewnpx skills add hiepdnh/Agentic-Development-Lifecycle --skill dev-reviewgit 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/dev-review)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/dev-review"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/dev-review.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.00088 | $0.02576 |
| Opus 5 | $0.00044 | $0.01288 |
| Sonnet 5 | $0.00018 | $0.00515 |
| Haiku 4.5 | $0.00009 | $0.00258 |
Grade A, and why
dev-review 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: /dev-review
Role: Developer / Tech Lead
Mục đích: Review toàn diện sau dev-implement — code quality, architecture, performance, security — trong 1 lần chạy. Kết quả là quyết định Approve / Request Changes trước khi chạy /dev-pr.
Hướng dẫn thực hiện
Bước 1 — Thu thập context (subagent)
Independent Harness Review (opt-in):
Nếu team có sẵn CLI/model khác ngoài harness đang chạy /dev-review này (ví dụ: code được implement bằng Claude Code nhưng máy có sẵn Codex CLI, Copilot CLI, hoặc OpenCode đã cấu hình) — khuyến nghị chạy review đó bằng công cụ khác thay vì cùng session/model đã implement, để giảm rủi ro "tự review chính mình" (reviewer blind-spot). Đây là gợi ý advisory, hoàn toàn opt-in — /dev-review không thể tự gọi CLI của vendor khác. Nếu chọn chạy cross-harness: thực hiện thủ công ở công cụ đó, sau đó quay lại ghi rõ harness nào đã review vào field harness của review-log.md (xem Bước 6). Nếu bỏ qua, tiếp tục review trong session hiện tại như bình thường.
Kiểm tra review round trước (nếu có):
Tìm docs/tasks/[TASK-ID]/review-log-R*.md. Nếu tồn tại:
- Load danh sách
B-xx(Blocking) từ round gần nhất - Dùng list đó để verify từng item đã được fix trong diff hiện tại
- Báo cáo rõ:
B-01 ✅ fixed/B-01 ❌ still present
Xác định base branch trước khi spawn:
Kiểm tra theo thứ tự:
- User cung cấp base branch trong lệnh (ví dụ:
/dev-review develop) - Đọc
git remote show originđể detect default branch - Nếu vẫn không rõ → dùng
AskUserQuestionhỏi base branch trước khi tiếp tục
Spawn review-reader agent (model: haiku) theo agents/review-reader.md với input:
GIT DIFF:
[git diff <BASE_BRANCH>..HEAD]
BASE_BRANCH: <tên branch đã xác định>
ANALYSIS PATH:
docs/tasks/[TASK-ID]/analysis.md
VERIFICATION PATH:
docs/tasks/[TASK-ID]/verification.md
Agent trả về JSON với code_signals, arch_signals, security_signals, review_priority, intent_alignment. Dùng kết quả này làm input cho Bước 3.
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 · 234 lines · 88 tokens per session scan A 3e8964209c83
dev-review is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 7d ago), licensed MIT. It adds 88 tokens to every session and 2,576 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…