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 Xiaowen-Jiang/agent-enterprise --skill sprint_planninggit clone --depth 1 https://github.com/Xiaowen-Jiang/agent-enterpriseWrote 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/xiaowen-jiang/agent-enterprise/sprint_planning)<a href="https://agentmods.dev/skills/xiaowen-jiang/agent-enterprise/sprint_planning"><img src="https://agentmods.dev/badge/skills/xiaowen-jiang/agent-enterprise/sprint_planning/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/xiaowen-jiang/agent-enterprise/sprint_planning"><img src="https://agentmods.dev/badge/skills/xiaowen-jiang/agent-enterprise/sprint_planning.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.00020 | $0.00423 |
| Opus 5 | $0.00010 | $0.00211 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
Sprint Planning 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 10d 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
Process
- Review the backlog — Understand pending work, priorities, and dependencies
- Assess team capacity — Who is available? Any blockers or time-off?
- Prioritize items — Must-have (P0), should-have (P1), nice-to-have (P2)
- Estimate effort — T-shirt sizes (S/M/L/XL) or story points
- Assign ownership — Match tasks to team members based on skills and availability
- Identify dependencies — What blocks what? External dependencies?
- Define sprint goal — One sentence describing what success looks like
Output Format
## Sprint Plan: [Sprint Name/Number]
**Goal**: [One-sentence sprint goal]
**Duration**: [Start date] - [End date]
**Team capacity**: [Available person-days]
### Must-Have (P0)
| Task | Owner | Size | Dependencies | Status |
|------|-------|------|-------------|--------|
| ... | ... | S/M/L | ... | To Do |
### Should-Have (P1)
| Task | Owner | Size | Dependencies | Status |
|------|-------|------|-------------|--------|
### Nice-to-Have (P2)
| Task | Owner | Size | Dependencies | Status |
|------|-------|------|-------------|--------|
### Risks & Blockers
- [Risk 1]: Mitigation plan
Guidelines
- Don't overcommit — leave 20% buffer for unplanned work
- Break large tasks into subtasks (nothing bigger than XL)
- Every task should have a clear definition of done
- Flag external dependencies early
- Balance workload across team members
- Include carry-over items from previous sprint
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.
- 10d ago First seen · 53 lines · 20 tokens per session scan A 204161a92cf0
Sprint Planning is a skill published in the GitHub repository Xiaowen-Jiang/agent-enterprise (52 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 423 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…
workspace-manager
Registers, lists, removes, and assigns workspaces (project directories) for Anima work. Use when: binding project paths to Anima, managing aliases, or switching workspace roots.
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.