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.
git clone --depth 1 https://github.com/YuDefine/nuxt-supabase-starterWrote 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/commands/yudefine/nuxt-supabase-starter/retro)<a href="https://agentmods.dev/commands/yudefine/nuxt-supabase-starter/retro"><img src="https://agentmods.dev/badge/commands/yudefine/nuxt-supabase-starter/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.00013 | $0.00443 |
| Opus 5 | $0.00006 | $0.00221 |
| Sonnet 5 | $0.00003 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
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 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
/retro — Sprint 回顧
Step 1: 收集指標
# 最近 commits（自上次 tag 或最近 7 天）
git log --since="7 days ago" --oneline --stat
# 變更統計
git diff --stat $(git describe --tags --abbrev=0 2>/dev/null || git rev-list --max-parents=0 HEAD)..HEAD
收集：
- Commit 數量
- 檔案變更數
- 新增/刪除行數
- PR 數量（
gh pr list --state merged --search "merged:>=$(date -v-7d +%Y-%m-%d)"或同等）
Step 2: 品質評分（0-10）
| 維度 | 評估方式 |
|---|---|
| Velocity | Commits/天、feature 完成率 |
| Quality | Test 覆蓋率、bug 修復比例 |
| Test Coverage | 新 feature 是否有配對測試 |
| Code Health | Refactor 比例、tech debt 處理 |
Step 3: Hotspot 分析
找出最常被修改的檔案（可能需要重構）：
git log --since="7 days ago" --name-only --pretty=format: | sort | uniq -c | sort -rn | head -10
Step 4: 報告
## Sprint Retro — [日期範圍]
### 📊 指標
- Commits: N
- Files changed: N
- Lines: +N / -N
### 📈 評分
| 維度 | 分數 | 備註 |
|------|------|------|
### 🔥 Hotspots
1. path/to/file (N changes)
2. ...
### 💡 建議
- [改善建議]
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 · 62 lines · 13 tokens per session scan A 69f2db1036ad
retro is a command published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 443 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 commands, from other repositories
implement
Execute tasks from a track's implementation plan following TDD workflow.
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
today
Create a morning heartbeat from repository state and update the local heartbeat log.
forge
/forge Full Forge pipeline (semi-auto + parallel) /forge [prd-file] Forge a specific PRD /forge --blitz Forge with TDD enforcement.
health-report
Show health status for all feature modules.
update-docs
Update living documentation so design, implementation, and validation stay aligned.