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 cenconq25/claude-code-app-studio --skill sprint-statusgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/sprint-status)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/sprint-status"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/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/skills/cenconq25/claude-code-app-studio/sprint-status"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/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.00047 | $0.01358 |
| Opus 5 | $0.00023 | $0.00679 |
| Sonnet 5 | $0.00009 | $0.00272 |
| Haiku 4.5 | $0.00005 | $0.00136 |
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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Status
A fast read of the in-flight sprint. Where things stand, what is at risk, what blocks. Read-only. Should complete in seconds.
Purpose / When to Run
Run when:
- The user asks "how is the sprint going" / "sprint status" / "where are we"
- Mid-sprint check-in
- Before standup, to prep
- After a story moves status, to confirm the snapshot updates
Distinct from /scope-check (which evaluates scope creep) and /milestone-review (broader scope).
Inputs
- The active sprint plan at
production/sprints/ - All story files in
production/epics/*/story-*.md production/session-state/active.md(optional)
Outputs
- Printed snapshot. No file writes.
Phase 1: Find the Active Sprint
Glob production/sprints/*.md sorted by filename (sprint-001, sprint-002, ...). The active sprint is:
- The one with
Status: Activein its header - Else the most recently dated one
If none exist, stop:
"No sprint plan found. Run
/sprint-plan newto create one."
If multiple have Status: Active, surface the conflict and ask which to report on.
Phase 2: Read Sprint Plan
Extract:
- Sprint number and slug
- Start and end dates
- Goal
- Backlog table with stories and statuses (the plan's view)
- Capacity
- Risks
Phase 3: Refresh from Story Files
The sprint plan's backlog table may be stale if engineers moved story Status without touching the plan. Re-read each story listed in the backlog:
- Current Status (Ready / In Progress / Blocked / Complete)
- Whether it's been touched recently (file mtime)
- Whether it has a
## Implementation Notesor## Mid-Story Updateblock (signals work in flight)
Build a fresh status tally:
- Total
- Complete
- In Progress
- Blocked
- Ready (not yet started)
Phase 4: Burndown Read
Compute:
- Days elapsed in sprint
- Days remaining
- Stories complete vs. total
- Implied velocity: complete / days elapsed
- Implied finish: total / velocity (in days)
Compare implied finish to days remaining:
- If implied finish ≤ days remaining → On track
- If implied finish ≤ days remaining × 1.2 → Tight
- If implied finish > days remaining × 1.2 → At risk
- If multiple stories Blocked → Blocked-heavy (mention even if other numbers look OK)
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.
- 6d ago First seen · 176 lines · 47 tokens per session scan A 2d18e8e8da32
sprint-status is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 1,358 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.