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 oxbshw/LLM-Agents-Ecosystem-Handbook --skill sprint-plannergit clone --depth 1 https://github.com/oxbshw/LLM-Agents-Ecosystem-HandbookWrote 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/oxbshw/llm-agents-ecosystem-handbook/sprint-planner)<a href="https://agentmods.dev/skills/oxbshw/llm-agents-ecosystem-handbook/sprint-planner"><img src="https://agentmods.dev/badge/skills/oxbshw/llm-agents-ecosystem-handbook/sprint-planner/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/oxbshw/llm-agents-ecosystem-handbook/sprint-planner"><img src="https://agentmods.dev/badge/skills/oxbshw/llm-agents-ecosystem-handbook/sprint-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00028 | $0.00422 |
| Opus 5 | $0.00014 | $0.00211 |
| Sonnet 5 | $0.00006 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
sprint-planner 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 11d 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 Planner
When to use
- Start of a sprint cycle
- After a re-prioritization mid-cycle
- When intake outpaces capacity and you need a defendable plan
When NOT to use
- Daily standup (different cadence)
- Annual planning (different scope; use
roadmap-synthesizer)
Inputs
| Name | Type | Required | Notes |
|---|---|---|---|
tickets |
list / path | yes | candidate work items with priority + estimates |
capacity |
object | yes | per-engineer days available |
previous_carry |
list | no | items rolling over from last sprint |
commitments |
list | no | OKR / stakeholder commitments that must land |
Outputs
sprint-plan.md with: Sprint goal, Committed, Stretch, Non-goals, Risks.
Workflow
- Compute total capacity (days × team)
- Sort candidates: committed → carry → stretch
- Pack to ~85% of capacity (leave room for support / interrupts)
- Identify dependencies between items; surface blockers
- Surface explicit non-goals — what we are not doing this sprint and why
- Risks: anything that would cause spillover
References
Success criteria
- Committed work ≤ 85% of capacity
- Every committed item has an owner and an estimate
- Non-goals section is non-empty
- Risks include at least one "what could derail us"
Failure modes
- Capacity unknown → ask, don't guess
- Tickets without estimates → flag and exclude from "committed"
What ships with it
1 file 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.
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.
- 11d ago First seen · 52 lines · 28 tokens per session scan A eea0e5278209
sprint-planner is a skill published in the GitHub repository oxbshw/LLM-Agents-Ecosystem-Handbook (546 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 422 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 skills, from other repositories
html-ppt-knowledge-arch-blueprint
OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.
beta-program-management
Running closed and open betas that produce real signal. Beta participant selection, structured feedback collection, beta-to-GA decision criteria, and the difference between soft-launch (no structure, no signal), kitchen-sink (everyone in, no actionable feedback), and structured beta (calibrated cohort, intentional…
okr-design
OKR design as actually shipped, not as conference-talk theory. Outcome statements that drive decisions, key results that measure the right thing, scoring discipline, mid-quarter recalibration, and the difference between sandbagged OKRs (always 100%) and aspirational OKRs (always 30%) and stretch OKRs (genuine ambition…
roadmap-planning
Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next…
product-frameworks
Product management frameworks for business cases, market analysis, strategy, prioritization, OKRs/KPIs, personas, requirements, and user research. Use when building ROI projections, competitive analysis, RICE scoring, OKR trees, user personas, PRDs, or usability testing plans.
html-ppt-graphify-dark-graph
OpenDesign's feature business case for the plugin marketplace: the user pain, options, tradeoffs, and the measure of success. Built as a decision-grade product management deck for PM, eng, design, leadership.