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/sm-retro/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/sm-retro)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/sm-retro"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/sm-retro.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.00067 | $0.00900 |
| Opus 5 | $0.00034 | $0.00450 |
| Sonnet 5 | $0.00013 | $0.00180 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
sm-retro 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 8d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: /sm-retro
Role: Scrum Master
Mục đích: Facilitate sprint retrospective, tổng hợp feedback, tạo action items có thể thực hiện được.
Hướng dẫn thực hiện
Bước 1 — Gate: Setup retro
## Tôi sẽ facilitate retro cho Sprint [N].
Trước khi bắt đầu:
| # | Câu hỏi | Lựa chọn |
|---|---------|---------|
| 1 | Format retro ưa thích? | A: Start/Stop/Continue / B: 4Ls (Liked/Learned/Lacked/Longed for) / C: Mad/Sad/Glad / D: Khác: ___ |
| 2 | Team size | _(điền số người)_ |
| 3 | Thời gian retro | _(điền số phút)_ |
| 4 | Có action items từ retro trước chưa done không? | A: Không / B: Có — [N] items chưa done / C: Khác: ___ |
Chờ confirm.
Bước 2 — Tổng hợp feedback
Nhận input từ team (paste anonymous feedback hay notes từ session).
Phân loại và nhóm themes:
# Sprint [N] Retrospective
**Date**: [Date]
**Facilitator**: [SM name]
**Attendees**: [N] people
**Sprint**: [N] | [Start date] → [End date]
---
## Sprint Highlights
- **Velocity**: [X] points ([+/-N%] vs previous sprint)
- **Delivered**: [N]/[M] planned items
- **Team health**: 🟢 Good / 🟡 OK / 🔴 Needs attention
---
## What Went Well ✅
### [Theme 1: e.g., "Collaboration"]
- [Specific observation]
- [Votes: N]
### [Theme 2]
...
---
## What Needs Improvement 🔧
### [Theme 1: e.g., "Requirements clarity"]
- [Specific observation]
- [Votes: N]
- [Suggested fix]
### [Theme 2]
...
---
## Action Items
| # | Action | Owner | Done by | Success metric |
|---|--------|-------|---------|----------------|
| 1 | [Specific action, not vague] | [Name] | Sprint [N+1] Day 1 | [...] |
| 2 | | | | |
---
## Action Items từ Retro trước
| Action | Owner | Status | Ghi chú |
|--------|-------|--------|---------|
| [Action từ Sprint N-1] | [Name] | ✅ Done / ❌ Not done / 🔄 In progress | [...] |
---
## Shoutouts 🌟
- [Member X] — [cụ thể tại sao được shoutout]
Bước 3 — Gate cuối
Retro summary đã soạn xong.
Tôi có [N] action items.
Câu hỏi quan trọng:
| # | Câu hỏi | Lựa chọn |
|---|---------|---------|
| 1 | Action item [X] — [Name] có accept ownership không? | A: Có / B: Không — assign lại cho: ___ / C: Khác: ___ |
| 2 | Action items có quá nhiều không? | A: Vừa đủ / B: Quá nhiều — cắt xuống top 2-3 / C: Khác: ___ |
| 3 | Có theme quan trọng bị gộp nhầm cần tách ra không? | A: Không / B: Có — theme: ___ / C: Khác: ___ |
| 4 | Action items cũ chưa done — cần escalate hay drop? | A: Escalate / B: Drop / C: Carry over thêm 1 sprint / D: Khác: ___ |
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.
- 8d ago First seen · 121 lines · 67 tokens per session scan A 7d9005fe49ed
sm-retro is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 11d ago), licensed MIT. It adds 67 tokens to every session and 900 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.