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 Notysoty/openagentskills --skill sprint-summary-generatorgit clone --depth 1 https://github.com/Notysoty/openagentskillsWrote 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/notysoty/openagentskills/sprint-summary-generator)<a href="https://agentmods.dev/skills/notysoty/openagentskills/sprint-summary-generator"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/sprint-summary-generator/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/notysoty/openagentskills/sprint-summary-generator"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/sprint-summary-generator.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.01790 |
| Opus 5.5 | $0.00008 | $0.00716 |
| Sonnet 5.5 | $0.00004 | $0.00358 |
| Haiku 4.5 | $0.00002 | $0.00179 |
Grade A, and why
Sprint Summary Generator 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 1mo 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Summary Generator
What this skill does
This skill takes a raw list of completed tickets, commit messages, or PR titles from a sprint and produces a polished sprint summary document suitable for stakeholders, leadership, or the whole team. It groups work into meaningful themes, translates technical changes into business language, flags blockers and carryover items, and formats everything for a Slack post, email, or wiki page.
Use this at the end of every sprint to save time writing the sprint review, or to quickly communicate what shipped to non-technical stakeholders.
How to use
Claude Code / Cline
Copy this file to .agents/skills/sprint-summary-generator/SKILL.md in your project root.
Then ask:
- "Use the Sprint Summary Generator skill. Here are our completed tickets: [paste list]."
- "Generate a sprint summary from this git log using the Sprint Summary Generator skill."
Provide:
- Sprint number or name
- Sprint dates (or just the duration, e.g., "2-week sprint ending 2026-03-15")
- List of completed tickets, PRs, or commits
- Any blockers or incomplete items
- Anything notable (incidents, team changes, major decisions)
Cursor
Add the instructions below to your .cursorrules or paste them into the Cursor AI pane. Paste the ticket list and any context before asking for the summary.
Codex
Paste all available information (ticket list, sprint dates, blockers) and ask Codex to follow the instructions below.
The Prompt / Instructions for the Agent
When asked to generate a sprint summary, follow these steps:
Step 1 — Parse and understand the work
For each completed item:
- Identify the user-facing or business impact (what changed for a user or the business?)
- Identify the theme or area (user-facing product, internal tooling, infrastructure, bug fixes, technical debt, etc.)
- Filter out noise (dependency bumps, formatting fixes, CI tweaks) — mention them briefly but don't feature them
- Note any items that were started but not completed (carryover)
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.
- 1mo ago First seen · 210 lines · 21 tokens per session scan A 928d8c232df6
Sprint Summary Generator is a skill published in the GitHub repository Notysoty/openagentskills (9 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 1,790 once invoked, about $0.0001 per session on Opus 5.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
meta-ad-manager
Front door and loop owner of a Meta (Facebook/Instagram) ad harness. Reads the brand's ads/ docs, works out which campaign the user means and which stage it is at, hands off to the stage skill that runs it (intake, strategy, creative, launch, checks, fixes, answers), and writes every stage change back to the docs. Use…
where-to-start-situation-save
Step of the where-to-start playbook: saves the founder's answers and the agreed first move with the brand, so later visits and other playbooks don't ask again. Run where-to-start instead; not for direct use.
mass-ulw
Drives dependency-ordered child work through the native workflow tool, each phase's stages defined up front in one run, with retry/amend/send recovery. Use when the user asks for mass-ulw, a DAG of tasks, or fan-out work where some tasks must wait on others.
fde
Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. Use when they prep a…
ingest
Fetch requested source material and prepare sourced engagement updates. Use to catch up from external notes or messages; applying updates requires a bound record and confirmation.
audit
Audit an inherited engagement or implementation against its evidence. Use when taking over work or joining mid-project; distinguish verified facts from inherited claims.