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 caipe-io/ai-platform-engineering --skill sprint-progress-reportgit clone --depth 1 https://github.com/caipe-io/ai-platform-engineeringWrote 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/caipe-io/ai-platform-engineering/sprint-progress-report)<a href="https://agentmods.dev/skills/caipe-io/ai-platform-engineering/sprint-progress-report"><img src="https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/sprint-progress-report.svg" alt="Measured on agentmods" 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.00046 | $0.00770 |
| Opus 5 | $0.00023 | $0.00385 |
| Sonnet 5 | $0.00009 | $0.00154 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
sprint-progress-report 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 8d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Progress Report
Query Jira to build a detailed sprint progress report including velocity, burndown, completion rates, and blockers.
Instructions
Phase 1: Sprint Data Collection (Jira Agent)
- Identify the current sprint:
- Get the active sprint from the team's Jira board
- Collect sprint name, start date, end date, and goal
- Fetch all sprint issues:
- Stories, tasks, bugs, and subtasks in the sprint
- For each: key, summary, status, assignee, story points, priority, labels
- Fetch sprint history (for velocity):
- Last 3-5 completed sprints
- Committed vs. completed story points per sprint
Phase 2: Metrics Calculation
- Burndown Metrics:
- Total committed story points
- Completed story points
- Remaining story points
- Percentage complete
- Days remaining in sprint
- Projected completion (on track / at risk / behind)
- Velocity:
- Average velocity over last 3-5 sprints
- Current sprint pace vs. average
- Velocity trend (increasing, stable, decreasing)
- Issue Distribution:
- By status (To Do, In Progress, In Review, Done)
- By type (Story, Bug, Task)
- By assignee (workload balance)
- By priority (Critical, High, Medium, Low)
Phase 3: Blocker & Risk Analysis
- Identify blockers:
- Issues with `blocked` status or `blocker` label
- Issues with no activity for >2 days while In Progress
- Issues with unresolved dependencies
- Identify risks:
- High-priority items still in To Do with <3 days remaining
- Unassigned items
- Items added mid-sprint (scope creep)
- Items removed from sprint (scope reduction)
Output Format
```markdown
Sprint Progress Report
Sprint: Sprint 24 - "Platform Reliability" Period: Feb 3 - Feb 14, 2026 | Days Remaining: 5 Sprint Goal: Improve platform monitoring and reduce incident response time
Summary
| Metric | Value |
|---|---|
| Committed | 34 story points (15 issues) |
| Completed | 21 story points (9 issues) |
| Remaining | 13 story points (6 issues) |
| Completion | 62% |
| Projection | On Track (avg velocity: 32 pts) |
| ``` |
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.
- 8d ago First seen · 85 lines · 46 tokens per session scan A 88d5403b7e19
sprint-progress-report is a skill published in the GitHub repository caipe-io/ai-platform-engineering (407 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 770 once invoked, about $0.0002 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
gsd-tools
Central utility skill for GSD operations. Provides config parsing, slug generation, timestamps, path operations, and orchestrates calls to other specialized skills. Acts as the unified entry point that the original gsd-tools.cjs provided via its lib/ modules (commands, config, core, init).
babysit-babysitter-issues
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
spec-driven-development
Specification creation and management for the Pilot Shell methodology. Covers semantic search, clarifying questions, structured spec generation, and iterative refinement.
cog-meeting-processing
Process meeting recordings and transcripts into decisions, action items, and team dynamics.
cog-onboarding
Personalize COG Second Brain workflow through role pack selection and vault initialization.
cog-team-intelligence
Cross-reference GitHub, Linear, Slack, and PostHog with bidirectional sync for team briefs.