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/installnpx skills add hiepdnh/Agentic-Development-Lifecycle --skill installgit 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/install)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/install"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/install.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.00069 | $0.01270 |
| Opus 5 | $0.00034 | $0.00635 |
| Sonnet 5 | $0.00014 | $0.00254 |
| Haiku 4.5 | $0.00007 | $0.00127 |
Grade A, and why
install 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: /install
Mục đích: Cài framework vào project hiện tại. Dùng file tools của Claude (không chạy shell) để tránh permission classifier block.
Input
Không cần argument. Skill tự detect:
- Source: thư mục chứa framework này (nơi file
/install/SKILL.mdtọa lạc =[SOURCE]/.claude/skills/) - Target: working directory hiện tại của Claude Code session
Hướng dẫn thực hiện
Bước 0 — Xác định paths
Dùng Glob/Read để tìm:
- Source root: thư mục cha 2 cấp của file này (
../../từ vị trí file này) - Target root:
$PWDcủa session hiện tại (từ working directory)
Hiển thị để user xác nhận:
Source : [SOURCE_PATH]
Target : [TARGET_PATH]
AskUserQuestion({
questions: [
{
question: "Xác nhận cài đặt framework từ Source vào Target ở trên?",
header: "Confirm",
multiSelect: false,
options: [
{ label: "Cài đặt", description: "Tiếp tục copy commands/agents/templates/workflows vào Target" },
{ label: "Hủy", description: "Dừng lại, không cài đặt gì" }
]
}
]
})
Chờ confirm trước khi tiếp tục.
Bước 1 — Copy .claude/skills/
Dùng Glob để list tất cả file trong [SOURCE]/.claude/skills/**/SKILL*.md. Skills là flat folders, mỗi folder chứa SKILL.md (VN) + SKILL.en.md + SKILL.ja.md.
Với mỗi file:
- Compute đường dẫn target:
[TARGET]/.claude/skills/[relative_path] - Nếu target file đã tồn tại → báo
[SKIP], không ghi đè - Nếu chưa tồn tại → dùng Read + Write để copy
Báo cáo từng file: [OK] hoặc [SKIP].
Bước 2 — Copy agents/
Glob [SOURCE]/agents/*.md. Copy từng file sang [TARGET]/agents/.
Skip nếu đã tồn tại.
Bước 3 — Copy templates/
Glob TẤT CẢ file trong [SOURCE]/templates/ (cả .md và .html). Copy từng file sang [TARGET]/templates/.
Skip nếu đã tồn tại.
Bước 4 — Copy docs/workflows/
Glob [SOURCE]/docs/workflows/*.md. Copy sang [TARGET]/docs/workflows/.
Skip nếu đã tồn tại.
Bước 4b — Copy framework doc files
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 · 145 lines · 69 tokens per session scan A c2852899c656
install is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 7d ago), licensed MIT. It adds 69 tokens to every session and 1,270 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.
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…