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 rampstackco/claude-skills --skill sprint-operationsgit clone --depth 1 https://github.com/rampstackco/claude-skillsWrote 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/rampstackco/claude-skills/sprint-operations)<a href="https://agentmods.dev/skills/rampstackco/claude-skills/sprint-operations"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills/sprint-operations/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/rampstackco/claude-skills/sprint-operations"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills/sprint-operations.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.00188 | $0.02659 |
| Opus 5.5 | $0.00075 | $0.01064 |
| Sonnet 5.5 | $0.00038 | $0.00532 |
| Haiku 4.5 | $0.00019 | $0.00266 |
Grade A, and why
sprint-operations 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- sprint-operations — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Operations
Run the measurement and ceremony layer of a delivery team so planning is grounded in history and reporting is derived from the tracker, not typed in. Tracker-agnostic: works with Jira, Linear, GitHub Issues, or your tracker of choice.
When to use
- Setting up the metric set for a new or inherited team
- Planning a sprint and checking it against real capacity
- Running standup, refinement, review, or retro with a consistent template
- Answering "how is the team doing?" with numbers instead of adjectives
- Writing the sprint report or the quarterly rollup
- Deriving a points-to-hours ratio for finance
- Measuring a team where some lanes are AI coding agents
When NOT to use
- Writing the tickets that go into the sprint (use
ticket-authoring) - Writing the narrative of a retrospective or postmortem (use
after-action-report) - Setting objectives and key results (use
okr-design) - Deciding what ships this quarter (use
roadmap-planning) - Writing the handoff for an agent lane (use
dispatch-authoring) - Shaping the readout for executives (use
stakeholder-communication)
Required inputs
- Tracker access or an export with created, started, done, reopened, and sprint fields per ticket
- The team roster and planned availability for the sprint
- The last three to six sprints of history, if they exist
- The team's estimation scale (points, t-shirt sizes, or counts)
- Finance requirements for hours, if the team capitalizes development
If there is no history, say so. The first three sprints set the baseline. Do not invent one.
The framework: 4 parts
Part 1: The measurement set
Eight metrics. Each is derived from tracker timestamps and fields. None is typed into a spreadsheet by hand.
| Metric | One-line definition | Computed as |
|---|---|---|
| Cycle time | How long work takes once started | done date minus started date, per ticket; report the median and 85th percentile |
| Lead time | How long a request waits plus takes | done date minus created date, per ticket; median and 85th percentile |
| Throughput | How much finishes | count of tickets moved to done in the period |
| WIP | How much is in flight | count of tickets in any started, not-done state, sampled daily |
| Carryover percent | How much of the plan spilled | committed tickets not done at sprint end, divided by committed tickets |
| Planned vs unplanned ratio | How much of the sprint was the plan | done tickets committed at planning, divided by all done tickets |
| Rework rate | How often done was not done | tickets reopened after done, divided by tickets done |
| Estimate accuracy | How well sizing predicts effort | per size bucket, the spread of cycle times; tighter is better |
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- README.md 358 B
- references/capacity-checklist.md 2.7 KB
- references/example-sprint-report.md 4.3 KB
- references/metrics-reference.md 5.9 KB
- references/planning-template.md 1.9 KB
- references/refinement-template.md 2.0 KB
- references/retro-template.md 2.5 KB
- references/review-template.md 1.5 KB
- references/sprint-report-template.md 2.3 KB
- references/standup-template.md 1.7 KB
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 · 177 lines · 188 tokens per session scan A 0ec7c2bee8cb
sprint-operations is a skill published in the GitHub repository rampstackco/claude-skills (995 stars, last pushed today), licensed MIT. It adds 188 tokens to every session and 2,659 once invoked, about $0.0008 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-10-20.
Other skills, from other repositories
skill-creation-walkthrough
Step-by-step guide for creating your own Claude Skills, from deciding whether a skill is the right tool to writing the SKILL.md file, structuring reference material, and making it trigger reliably. Use when you want to package a workflow, framework, or repeated task into a reusable Skill, when an existing skill is not…
mass-ulw
Drives dependency-ordered child work through the native workflow tool, each phase's stages defined up front in one run, with retry/amend/send recovery. Use when the user asks for mass-ulw, a DAG of tasks, or fan-out work where some tasks must wait on others.
crm-data-cleanup
Cleans up CRM data from HubSpot, Salesforce, Pipedrive, Zoho, Close, Attio, or any CRM CSV export. Finds duplicate contacts and companies with fuzzy matching (not just exact email), normalizes emails, phones to E.164, names, domains, states, and countries, flags stale, invalid, role, and test records, finds broken…
multi-agent-client-onboarding
Uses Agent SDK to deploy 3 parallel agents for client onboarding -- workflow auditor, tech stack mapper, and strategy drafter. Real consulting workflow that produces a complete client assessment.
meeting-intelligence
Analyze meeting transcripts to extract decisions, action items, blockers, sentiment, and generate follow-up emails. Use when user provides meeting notes, transcripts, or recordings and needs structured summaries or action tracking.
session-handoff
Use when a working session is ending, the context window is nearly full, work needs to pass to a teammate or a fresh session, or the user says "hand this off", "write this up before we lose it", "I'm starting a new session", or "summarize where we are". Produces a handoff document that lets the next session resume…