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-standup/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-standup)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/sm-standup"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/sm-standup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/sm-standup"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/sm-standup.svg" alt="Reviewed on agentmods" width="80" 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.00068 | $0.00569 |
| Opus 5 | $0.00034 | $0.00284 |
| Sonnet 5 | $0.00014 | $0.00114 |
| Haiku 4.5 | $0.00007 | $0.00057 |
Grade A, and why
sm-standup 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.
What it actually says
Skill: /sm-standup
Role: Scrum Master / Team
Mục đích: Tổng hợp và format daily standup nhanh, highlight blockers.
Hướng dẫn thực hiện
Bước 1 — Thu thập input
Nhận input từ team (paste nội dung thô từ Slack/chat hoặc danh sách từng người):
## Paste standup updates của team vào đây.
Format input không quan trọng — text thô, bullet points, hay prose đều OK.
Tôi sẽ format lại cho chuẩn.
Cần biết thêm: Sprint [N] kết thúc khi nào?
Bước 2 — Tổng hợp và format
# Daily Standup — [Date]
**Sprint [N]** | **Day [X]/[Y]**
---
## Team Updates
### [Tên member 1]
- ✅ **Hôm qua**: [...]
- 🔄 **Hôm nay**: [...]
- ⛔ **Blockers**: [None / Mô tả]
### [Tên member 2]
...
---
## 🚨 Blockers cần action
| Người | Blocker | Cần hỗ trợ từ |
|-------|---------|--------------|
| | | |
## ⚠️ Sprint Health
- Tasks completed: [N]/[Total]
- Days remaining: [X]
- At-risk items: [list nếu có]
## 📌 Follow-up
- [Action item từ hôm qua đã xong chưa?]
Bước 3 — Gate: Highlight concerns
Standup tổng hợp xong.
Tôi nhận thấy:
| # | Quan sát | Lựa chọn |
|---|---------|---------|
| 1 | [Member X] bị block [N] ngày — cần escalate không? | A: Escalate ngay / B: Để thêm 1 ngày / C: Không cần / D: Khác: ___ |
| 2 | Task [Y] at risk — chỉ còn [Z] ngày | A: Cần hỗ trợ thêm / B: Đang xử lý / C: Đã scope lại / D: Khác: ___ |
| 3 | Velocity bất thường — có gì tôi miss không? | A: Không miss gì / B: Có — context: ___ / C: Khác: ___ |
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.
- 8d ago First seen · 82 lines · 68 tokens per session scan A e922029e10f9
sm-standup is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 11d ago), licensed MIT. It adds 68 tokens to every session and 569 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.