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/sprint-status)<a href="https://agentmods.dev/commands/yudefine/nuxt-supabase-starter/sprint-status"><img src="https://agentmods.dev/badge/commands/yudefine/nuxt-supabase-starter/sprint-status/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/commands/yudefine/nuxt-supabase-starter/sprint-status"><img src="https://agentmods.dev/badge/commands/yudefine/nuxt-supabase-starter/sprint-status.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.00011 | $0.00315 |
| Opus 5 | $0.00005 | $0.00158 |
| Sonnet 5 | $0.00002 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
sprint-status 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-status — 開發狀態 Dashboard
Step 1: Branch 概覽
git branch -a --sort=-committerdate | head -10
git log --oneline -5
Step 2: 未完成工作
# 未提交的變更
git status --porcelain
# 未 push 的 commits
git log origin/HEAD..HEAD --oneline 2>/dev/null
# Stash
git stash list
Step 3: Spectra 狀態
# 列出 active changes
ls openspec/changes/ 2>/dev/null
如果有 active changes，顯示其 tasks 完成進度。
Step 4: CI/CD 狀態
gh run list --limit 3 2>/dev/null
Step 5: 輸出 Dashboard
## 📋 Sprint Status
### 🌿 Current Branch: <branch>
- Last commit: <hash> <message>
- Ahead of origin: N commits
### 📝 Working Tree
- Modified: N files
- Untracked: N files
- Stashed: N entries
### 📐 Spectra Changes
- [change-name]: N/M tasks done
### 🚀 CI/CD
- Latest run: ✅/❌ <workflow> (<time>)
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 · 62 lines · 11 tokens per session scan A 2a41a475a5a4
sprint-status is a command published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 315 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
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
weekly-summary
Generate weekly work summary from git activity.
update-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
parallel
You are executing the /hydra:parallel command. Start multiple agents simultaneously in different worktrees.
cd-branch
Create a Conductor branch CARD and brief (does not open a session). Master only.
gh-issue
File a groomed, dispatchable GitHub issue from a breadcrumb (component/page/object) plus a problem description — recon the code, verify evidence, dedupe, label, file. Optionally pin the dispatch model/effort. Example — /gh-issue "Settings > Billing > Invoice row" clicking an invoice opens a 404 model:opus effort:high.