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/docs-projectnpx skills add hiepdnh/Agentic-Development-Lifecycle --skill docs-projectgit 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/docs-project)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/docs-project"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/docs-project.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.00103 | $0.01550 |
| Opus 5 | $0.00051 | $0.00775 |
| Sonnet 5 | $0.00021 | $0.00310 |
| Haiku 4.5 | $0.00010 | $0.00155 |
Grade B, and why
docs-project scanned grade B with 1 finding 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
- [ ] Cấu trúc thư mục có khớp với `ls .claude/skills/` không? How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: /docs-project
Role: Developer / Tech Lead / DevOps
Mục đích: Đồng bộ tất cả tài liệu project-level (README, guides, install scripts, CLAUDE.md) với trạng thái thực tế của codebase.
Phân biệt với /docs-update
| Skill | Dùng cho | Trigger |
|---|---|---|
/docs-update |
Baseline screen + API docs sau task verify | Sau mỗi task merge |
/docs-project |
README, workflow, install, CLAUDE.md | Khi project thay đổi lớn |
Hướng dẫn thực hiện
Bước 1 — Xác định scope
Đọc các file sau để hiểu trạng thái hiện tại:
README.md(hoặcREADME.vi.mdnếu có)CLAUDE.mddocs/workflows/*.mdbin/install.js,setup.sh,setup.ps1(nếu có)package.json(scripts, version, dependencies)pubspec.yaml(nếu Flutter project).claude/settings.json
Dùng AskUserQuestion tool để hỏi:
-
Loại update: Bạn muốn cập nhật phần nào?
README— nội dung giới thiệu, quick start, badgesWorkflow guides— docs/workflows/*.md (sprint lifecycle, role guide)Install scripts— bin/install.js, setup.sh, setup.ps1CLAUDE.md— skill commands, cấu trúc thư mục, project contextTất cả— scan toàn bộ và đề xuất những gì lỗi thời
-
Nguồn thay đổi: Thay đổi đến từ đâu?
- Code/feature mới vừa merge
- Skill commands mới được thêm
- Team/process thay đổi
- Onboarding developer mới (cần review toàn bộ)
Chờ confirm.
Bước 2 — Audit: Tìm nội dung lỗi thời
Với mỗi file trong scope, so sánh nội dung hiện tại với thực tế:
README audit checklist:
- Version number / badges còn đúng không?
- Quick start steps có chạy được không? (test từng lệnh)
- Prerequisites list có thiếu tool nào mới không?
- Screenshot/demo có lỗi thời không?
- Link đến docs có còn valid không?
CLAUDE.md audit checklist:
- Skill commands table có đủ 22+ skills không?
- Cấu trúc thư mục có khớp với
ls .claude/skills/không? - Subagent table trong
agents/có đúng không? - Project Context có cần update project name / repo URL không?
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 · 181 lines · 103 tokens per session scan B 38f2670162c5
docs-project is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 7d ago), licensed MIT. It adds 103 tokens to every session and 1,550 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). 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…