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 FortiumPartners/ensemble --skill ensemble-sprint-statusgit clone --depth 1 https://github.com/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/ensemble-sprint-status)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/ensemble-sprint-status"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-sprint-status/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/fortiumpartners/ensemble/ensemble-sprint-status"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-sprint-status.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.00026 | $0.00259 |
| Opus 5 | $0.00013 | $0.00130 |
| Sonnet 5 | $0.00005 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
ensemble-sprint-status 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
Ensemble Command: /ensemble:sprint-status
This Codex skill mirrors the Ensemble slash command /ensemble:sprint-status.
Follow the workflow below, adapt to the current repository, and keep outputs structured.
Generate a comprehensive sprint status report including task completion percentages, blockers, team velocity, and projected completion date based on current TRD progress.
Workflow
Phase 1: Data Collection
1. TRD Analysis Scan TRD files for task checkboxes
2. Progress Calculation Calculate completion percentages
Phase 2: Report Generation
1. Status Report Generate formatted status report
Expected Output
Format: Sprint Status Report
Structure:
- Completion Summary: Overall and per-category completion percentages
- Blockers: Identified blockers and dependencies
- Velocity: Team velocity and projected completion
Usage
/ensemble:sprint-status
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 · 48 lines · 26 tokens per session scan A 06accff55db2
ensemble-sprint-status is a skill published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 259 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
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.
bmad-check-implementation-readiness
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
bmad-correct-course
Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change".
bmad-create-story
Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]".
bmad-retrospective
Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]".
bmad-document-project
Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs".