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-retrogit 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-retro)<a href="https://agentmods.dev/skills/stanshy/agenthub/sprint-retro"><img src="https://agentmods.dev/badge/skills/stanshy/agenthub/sprint-retro/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-retro"><img src="https://agentmods.dev/badge/skills/stanshy/agenthub/sprint-retro.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.00014 | $0.00305 |
| Opus 5 | $0.00007 | $0.00152 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
sprint-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 9d 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 回顧
自動帶入第 10 節數據，產出回顧報告。
使用方式
/sprint-retro <sprint-number>
參數
$0: Sprint 編號
執行步驟
-
讀取 dev-plan 第 10 節： !
cat proposal/sprint$0-dev-plan.md 2>/dev/null | grep -A 100 "任務與審核紀錄" -
讀取提案書驗收標準： !
cat proposal/sprint$0-proposal.md 2>/dev/null | grep -A 30 "驗收標準" -
分析並產出回顧：
- 完成狀況：任務完成率、準時率
- 品質指標：Review 通過率、Gate 通過率
- 時程分析：預估 vs 實際
- 做得好的：值得延續的做法
- 需改進的：下次 Sprint 要注意的
- 行動項目：具體改善措施
-
寫入
proposal/sprint$0-retro.md
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.
- 9d ago First seen · 36 lines · 14 tokens per session scan A 5718b2db8203
sprint-retro is a skill published in the GitHub repository Stanshy/AgentHub (201 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 305 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
cross-campaign
Discover and reference other camps, projects, and files across camp boundaries. Use when the user mentions another camp or campaign by name, references work done "in another project/camp", or needs to find/copy/compare code across camps.
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.
fest-planning
Plan and scaffold festivals. Use when creating festival/phase/sequence/task structure, enforcing naming rules, linking festivals to projects, and promoting lifecycle states.
camp-workitems
Find, filter, choose, create, or adopt camp work items with camp workitem, camp wi, or camp workitems. Use when a user wants current active work across intents, designs, explore notes, festivals, or tracked workflow directories; when agents need safe camp workitem --json output; or when creating/adopting tracked…
fest-methodology
Use when the user mentions festivals, the fest CLI, phases, sequences, or tasks, or when working inside a festivals/ directory. Provides the core Festival methodology model so Claude understands the planning system.
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.