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 kieutrongthien/skills-fullstack --skill plan-sprint-managementgit clone --depth 1 https://github.com/kieutrongthien/skills-fullstackWrote 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/kieutrongthien/skills-fullstack/plan-sprint-management)<a href="https://agentmods.dev/skills/kieutrongthien/skills-fullstack/plan-sprint-management"><img src="https://agentmods.dev/badge/skills/kieutrongthien/skills-fullstack/plan-sprint-management/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/kieutrongthien/skills-fullstack/plan-sprint-management"><img src="https://agentmods.dev/badge/skills/kieutrongthien/skills-fullstack/plan-sprint-management.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.00021 | $0.00692 |
| Opus 5 | $0.00010 | $0.00346 |
| Sonnet 5 | $0.00004 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
plan-sprint-management 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Management Skill
What it does
- Plans sprint scope, capacity, and goals.
- Monitors execution via burndown, burnup, and velocity trends.
- Facilitates mid-sprint adjustments and end-of-sprint review/retro.
When to use
- When setting or recalibrating team capacity and commitments.
- When burndown deviates or blockers threaten the goal.
Key operations
- Identify active project; read
PROJECT.md, backlog,current-sprint.json,sprint-history.md. - Capacity planning: team availability, carry-over analysis, velocity guidance.
- Scope selection: pull stories by priority and capacity; set sprint goal.
- Tracking: daily burndown/burnup, WIP limits, blocker log; update
current-sprint.json. - Closeout: demo checklist, retro inputs, carry-over handling; update
sprint-history.mdand reports. - Log decisions and changes in
memory/YYYY-MM-DD.md.
Output files
projects/<ACTIVE>/sprints/current-sprint.json— active sprint scope, goal, capacity, burndown.projects/<ACTIVE>/sprints/sprint-[N].json— snapshots per sprint.projects/<ACTIVE>/sprints/sprint-history.md— retrospectives, velocity notes.projects/<ACTIVE>/reports/burndown-chart.json— burndown/burnup data (if generated).projects/<ACTIVE>/reports/velocity-chart.json— velocity trends.projects/<ACTIVE>/sprints/plan.md(optional) — capacity, goals, committed stories, dependencies.projects/<ACTIVE>/sprints/blockers.md— blockers, owners, ETAs, mitigation.memory/YYYY-MM-DD.md— sprint decisions, risks, adjustments.
Example workflow
- Capture capacity and carry-over; set sprint goal; update
current-sprint.json. - Select stories by priority; confirm acceptance criteria and estimates; commit scope.
- Track daily burndown; log blockers; adjust scope/WIP if needed; update
burndown-chart.json. - Close sprint: demo/review, retro notes, velocity update, carry-over to next sprint; update
sprint-[N].json,sprint-history.md, reports.
Best practices
- Keep WIP limited; favor finishing over starting new.
- Maintain a clean blocker log with owners and due dates.
- Re-estimate only when scope changes materially.
- Use velocity as a guide, not a target; avoid over-commitment.
- Maintain buffer (10–20%) and keep planned points ≤ velocity × 1.1.
- Record deviations and decisions in memory and sprint-history for transparency.
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 · 54 lines · 21 tokens per session scan A aa4c0bc38c1e
plan-sprint-management is a skill published in the GitHub repository kieutrongthien/skills-fullstack (2 stars, last pushed 7mo ago), licensed MIT. It adds 21 tokens to every session and 692 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-31.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.