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/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/stanshy/agenthub/sprint-close"><img src="https://agentmods.dev/badge/skills/stanshy/agenthub/sprint-close.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.00018 | $0.00488 |
| Opus 5.5 | $0.00007 | $0.00195 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 61 lines · 18 tokens per session scan A d95da0e8487e
sprint-close is a skill published in the GitHub repository Stanshy/AgentHub (204 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 488 once invoked, about $0.0001 per session on Opus 5.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
task-final-report
Apply the final report and PR publication procedure for a Hyper-Waterfall task. Write the final report (report.md), mark the daily task board complete, create the final commit, push the remote publish/task{N} branch, and create an Open PR to {BASEBRANCH}. Invoke only immediately before PR publication after all stages…
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.
operating-github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.