Borrowing it
Nothing to install: this file belongs to hiepdnh/Agentic-Development-Lifecycle. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hiepdnh/Agentic-Development-Lifecycle/main/.claude/skills/arch-adr/SKILL.mdgit 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/arch-adr)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/arch-adr"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/arch-adr.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.1 | $0.00058 | $0.00622 |
| Opus 5 | $0.00029 | $0.00311 |
| Sonnet 5 | $0.00012 | $0.00124 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
arch-adr 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 6d 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.
What it actually says
Skill: /arch-adr
Role: Tech Lead / Architect
Mục đích: Tạo Architecture Decision Record để document quyết định kiến trúc quan trọng.
Hướng dẫn thực hiện
Bước 1 — Gate: Thu thập context
## Tôi sẽ tạo ADR cho quyết định: [tên]
Để soạn ADR đầy đủ, cho tôi biết:
| # | Câu hỏi | Lựa chọn |
|---|---------|---------|
| 1 | Vấn đề / context dẫn đến quyết định này? | _(điền vào)_ |
| 2 | Những phương án nào đã được cân nhắc? | _(điền vào)_ |
| 3 | Tại sao chọn phương án hiện tại? | _(điền vào)_ |
| 4 | Ai là người ra quyết định? | _(điền vào)_ |
Bước 2 — Tạo ADR
Tạo file docs/decisions/ADR-[NNN]-[slug].md dùng template templates/adr.md.
Điền đầy đủ các section:
- Context: tình huống + constraints dẫn đến quyết định
- Quyết định: dứt khoát, không mơ hồ
- Các phương án đã cân nhắc: tối thiểu 2, bao gồm phương án đã chọn
- Hệ quả: tích cực + tiêu cực/trade-offs
- Điều kiện để revisit: trigger cụ thể (không phải "khi cần")
Bước 3 — Gate cuối
ADR-[NNN] đã soạn xong.
Câu hỏi trước khi finalize:
| # | Câu hỏi | Lựa chọn |
|---|---------|---------|
| 1 | "Hệ quả tiêu cực" có đủ honest không? | A: Đủ rồi / B: Cần thêm — cụ thể: ___ / C: Khác: ___ |
| 2 | "Điều kiện để revisit" có realistic không? | A: Có, hợp lý / B: Không — sửa lại: ___ / C: Khác: ___ |
| 3 | Có team member nào cần review trước khi accept? | A: Không cần / B: Có — tag: ___ / C: Khác: ___ |
Sau khi confirm, tôi sẽ update trạng thái sang "Accepted".
Sau khi ADR chuyển sang "Accepted", gợi ý chạy node bin/generate-project-context.js để refresh digest tự động docs/project-context.md (không hand-edit file này).
Chờ confirm.
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.
- 6d ago First seen · 62 lines · 58 tokens per session scan A 4976c1424c09
arch-adr is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 9d ago), licensed MIT. It adds 58 tokens to every session and 622 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…