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 agents/hiepdnh/agentic-development-lifecycle/doc-updatergit 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/agents/hiepdnh/agentic-development-lifecycle/doc-updater)<a href="https://agentmods.dev/agents/hiepdnh/agentic-development-lifecycle/doc-updater"><img src="https://agentmods.dev/badge/agents/hiepdnh/agentic-development-lifecycle/doc-updater.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.00000 | $0.00627 |
| Opus 5 | $0.00000 | $0.00313 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
doc-updater 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 5d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: doc-updater
Type: Subagent (spawned by docs-update)
Scope: Đọc baseline docs + diff-reader output, tạo doc update proposals. Không tự apply.
Recommended model: sonnet — proposals require accurate technical writing and context synthesis.
Input
DIFF READER OUTPUT:
[JSON từ diff-reader — docs_update_needed list]
CURRENT DOC CONTENT:
[Nội dung hiện tại của từng file cần update]
CHANGES SUMMARY:
[changes_summary từ diff-reader]
Nhiệm vụ
Với mỗi file trong docs_update_needed, tạo proposal cụ thể:
- Thêm gì mới
- Thay đổi gì (old → new)
- Xóa gì (không còn đúng)
Output format
Trả về JSON duy nhất trong markdown code block. Không prose, không giải thích thêm.
{
"proposals": [
{
"file": "docs/api/auth/login.md",
"reason": "Response schema thêm field otp_required",
"changes": [
{
"type": "add",
"location": "Response Success section — bảng fields",
"content": "| `otp_required` | boolean | True nếu account cần OTP verification |"
},
{
"type": "modify",
"location": "Mô tả endpoint",
"old": "Returns JWT token immediately",
"new": "Returns JWT token, hoặc redirect sang OTP flow nếu otp_required=true"
}
],
"uncertain": []
},
{
"file": "docs/screens/login/screen.md",
"reason": "New OTP step added to login flow",
"changes": [
{
"type": "add",
"location": "States table",
"content": "| OTP | Hiện OTP input form, ẩn password form |"
}
],
"uncertain": [
"OTP timeout duration — không thấy trong diff, cần confirm"
]
}
],
"no_change_needed": [
{
"file": "docs/screens/register/screen.md",
"reason": "Không bị ảnh hưởng bởi OTP changes"
}
]
}
Quy tắc
- Không apply thay đổi — chỉ propose
- Mỗi change phải có
locationcụ thể để người đọc biết chỉnh ở đâu - Nếu không chắc nội dung mới → ghi vào
uncertain, không tự suy diễn - Docs mô tả hành vi hiện tại (sau change), không phải lịch sử
- Xóa thông tin cũ hẳn, không comment out
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.
- 5d ago First seen · 100 lines · 0 tokens per session scan A fc5b0c5fc8e6
doc-updater is an agent published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 627 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.