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/matteocervelli/llmsWrote 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/matteocervelli/llms/user-story-sprint)<a href="https://agentmods.dev/commands/matteocervelli/llms/user-story-sprint"><img src="https://agentmods.dev/badge/commands/matteocervelli/llms/user-story-sprint/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/matteocervelli/llms/user-story-sprint"><img src="https://agentmods.dev/badge/commands/matteocervelli/llms/user-story-sprint.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.01706 |
| Opus 5 | $0.00007 | $0.00853 |
| Sonnet 5 | $0.00003 | $0.00341 |
| Haiku 4.5 | $0.00001 | $0.00171 |
Grade A, and why
user-story-sprint 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 5d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Sprint with Capacity Management
Plan a sprint by selecting stories based on capacity, dependencies, and priority.
Usage
/user-story-sprint <capacity>
/user-story-sprint <capacity> --buffer <percentage>
Examples
/user-story-sprint 40
/user-story-sprint 40 --buffer 20
/user-story-sprint 50 --dry-run
What it does
- Load Backlog - Loads stories with status "backlog" or "ready"
- Check Dependencies - Verifies dependency readiness
- Sort by Priority - Orders stories (critical → high → medium → low)
- Calculate Capacity - Applies buffer for unknowns
- Fit Stories - Selects stories up to capacity
- Validate Plan - Checks feasibility
- Update Status - Moves stories to sprint
- Create Milestone - Creates GitHub milestone (if enabled)
Result
- Sprint plan with selected stories
- Capacity breakdown (used/available/buffer)
- Dependency validation
- Story status updates (backlog → ready)
- GitHub milestone creation (if enabled)
Activate the sprint-planner skill to plan a sprint with capacity management.
Use the sprint-planner skill located in .claude/skills/sprint-planner/SKILL.md.
Parameters
- capacity: Sprint capacity in story points (required)
- --buffer: Buffer percentage (default: 20%)
- --dry-run: Show plan without making changes
- --sprint-name: Custom sprint name (default: auto-generated)
Sprint Planning Process
1. Capacity Calculation
Total Capacity: 40 points
Buffer (20%): 8 points
Available for Stories: 32 points
The buffer reserves capacity for:
- Bug fixes
- Support requests
- Technical debt
- Unknown complexity
2. Story Selection Criteria
Stories must meet ALL criteria:
- ✅ Status is "backlog" or "ready"
- ✅ All blocking dependencies are "done"
- ✅ Story points are estimated
- ✅ Acceptance criteria exist
- ✅ INVEST validation passed
3. Priority Sorting
Stories are sorted:
- Critical - Must be in sprint
- High - Important features
- Medium - Standard priority
- Low - Nice-to-have
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.
- 5d ago First seen · 241 lines · 14 tokens per session scan A 733c9612063c
user-story-sprint is a command published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 1,706 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-09-03.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.