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 skills add Stanshy/AgentHub --skill sprint-closegit clone --depth 1 https://github.com/Stanshy/AgentHubWrote 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/stanshy/agenthub/sprint-close)<a href="https://agentmods.dev/skills/stanshy/agenthub/sprint-close"><img src="https://agentmods.dev/badge/skills/stanshy/agenthub/sprint-close.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.00018 | $0.00488 |
| Opus 5 | $0.00009 | $0.00244 |
| Sonnet 5 | $0.00004 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
sprint-close 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 7d 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
Sprint 結案
老闆 + PM 確認所有 Gate 通過後執行，將 sprint branch merge 回 base branch。
使用方式
/sprint-close <sprint-number>
參數
$0: Sprint 編號（如1）
執行步驟
-
確認所有任務已完成： 使用 Glob tool 搜尋
.tasks/sprint-$0/*.md，用 Read tool 逐一讀取，確認所有任務| 狀態 |欄位均為done。 若有任一非done→ 列出未完成任務，停止執行。 -
讀取 base branch： 使用 Glob tool 搜尋
proposal/sprint$0-dev-plan.md，用 Read tool 讀取，找到| Base Branch |欄位取得 base branch 名稱（如main或master）。 -
切換並 merge：
git checkout {base-branch} git merge --no-ff sprint-$0 -m "release: sprint-$0 結案" -
建立 Tag：
git tag sprint-$0-release -
清理已 merge 的 task branches：
git branch --merged {base-branch} | grep "task/s$0-" | xargs git branch -d只刪除已完整 merge 進 base branch 的 task branches，未 merge 的保留並輸出警告。
-
刪除 sprint branch：
git branch -d sprint-$0 -
輸出結案摘要：
✅ Sprint $0 結案完成
Base Branch：{base-branch}
Tag：sprint-$0-release
清理 branches：{已刪除的 branch 列表，或「無」}
git log --oneline -5 顯示最近 commit：
{輸出}
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.
- 7d ago First seen · 61 lines · 18 tokens per session scan A d95da0e8487e
sprint-close is a skill published in the GitHub repository Stanshy/AgentHub (201 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 488 once invoked, about $0.0001 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-30.
Other skills, from other repositories
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
ijfw-ship
Use when the user says 'ship it', 'ship this', 'release', 'publish', 'launch', 'deploy', 'go live', 'wrap this up', 'time to ship', or invokes '/ijfw-ship'. Domain-aware release — software (test → tag → push → publish), book (final edit → format → KDP / agent / Substack), campaign (review → schedule → launch →…
aiwg-delivery-pr
AIWG-specific delivery pull request workflow; explicit alias for aiwg-pr, not a generic repository PR guide.
fest-execution
Execute active festival tasks. Use when finding the next task, marking tasks completed/blocked/reset, committing with festival traceability, advancing workflow steps, and validating sequence progress.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
camp-projects
Manage a camp's projects. Use when committing inside projects/, deciding status/pull/push scope (root vs submodule vs all), or creating/removing project worktrees.