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.
git clone --depth 1 https://github.com/felipecabargas/gambitWrote 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/agents/felipecabargas/gambit/sprint-to-stakeholders)<a href="https://agentmods.dev/agents/felipecabargas/gambit/sprint-to-stakeholders"><img src="https://agentmods.dev/badge/agents/felipecabargas/gambit/sprint-to-stakeholders/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/agents/felipecabargas/gambit/sprint-to-stakeholders"><img src="https://agentmods.dev/badge/agents/felipecabargas/gambit/sprint-to-stakeholders.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.00107 | $0.01220 |
| Opus 5 | $0.00053 | $0.00610 |
| Sonnet 5 | $0.00021 | $0.00244 |
| Haiku 4.5 | $0.00011 | $0.00122 |
Grade A, and why
sprint-to-stakeholders 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 9d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint to Stakeholders Agent
Overview
This agent is a three-skill chain that turns raw sprint data into a complete communications package. It runs sprint-review, write-release-notes, and write-stakeholder-update in sequence, producing one internal artefact and two external-facing artefacts from a single sprint data input.
The three components and what each produces:
- sprint-review — processes sprint ticket data, team velocity, and a sprint goal to produce a structured internal review document covering what shipped, what slipped, and key takeaways
- write-release-notes — filters the completed work list for customer-visible items and formats them as user-facing release notes, ready to publish
- write-stakeholder-update — synthesises the sprint review highlights and release notes into a concise stakeholder update suitable for leadership, investors, or cross-functional partners
Chain
sprint-review → write-release-notes → write-stakeholder-update
How It Runs
Step 1 — Run Sprint Review
Run sprint-review using the provided sprint data (sprint name or number, ticket list, team notes, or any combination). The skill produces a structured internal review covering the sprint goal, completed items, slipped items, blockers, and retrospective highlights.
Save output as sprint-review-[slug].md, where [slug] is derived from the sprint name or number (e.g. sprint-review-sprint-42.md).
Pause here only if the sprint data is ambiguous — for example, if no sprint goal is present or it is unclear which tickets were completed vs. in-progress. If the data is sufficient, proceed automatically.
Step 2 — Write Release Notes
Feed the completed work list from Step 1 into write-release-notes. Filter for customer-visible items only — exclude internal refactors, infrastructure changes, dependency bumps, and anything flagged as internal. Format the remaining items as user-facing release notes with a short summary of what changed and why it matters to users.
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.
- 9d ago First seen · 87 lines · 107 tokens per session scan A fec360691f9c
sprint-to-stakeholders is an agent published in the GitHub repository felipecabargas/gambit (2 stars, last pushed 3mo ago), licensed MIT. It adds 107 tokens to every session and 1,220 once invoked, about $0.0005 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 agents, from other repositories
support-assistant
Use when: handling helpdesk tickets, technical support, or customer service conversations. Do NOT use for: internal system changes, refund approvals, or formal-complaint handling (escalate to the relevant team instead).
project-manager
Project delivery specialist. Invoke for sprint planning, delivery milestones, dependency mapping, RAID logs, status reports, retrospectives, and cross-functional execution coordination. Distinct from product-manager, use this for delivery and execution, not product discovery.
technical-business-analyst
Technical business analysis specialist. Invoke for implementation plans, user stories, requirements documents, functional specifications, scope definition, gap analysis, ADRs, RAID logs, and task decomposition. Returns structured documents with exact detail, no placeholders.
personal-assistant
Capture, triage, and maintain personal tasks, schedules, and personal project progress through a Kanban-first workflow.
prd-planner
Clarify product requirements, scope, acceptance criteria, and product decisions.
pmo
Enterprise PMO. Owns plugins/pmo/ and nothing else. Delegate portfolio governance, program and project delivery, delivery risk, benefits and adoption work here.