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 abrahamFerga/scrum-skills --skill po-release-notesgit clone --depth 1 https://github.com/abrahamFerga/scrum-skillsWrote 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/abrahamferga/scrum-skills/po-release-notes)<a href="https://agentmods.dev/skills/abrahamferga/scrum-skills/po-release-notes"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/po-release-notes/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/abrahamferga/scrum-skills/po-release-notes"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/po-release-notes.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.00103 | $0.01378 |
| Opus 5 | $0.00051 | $0.00689 |
| Sonnet 5 | $0.00021 | $0.00276 |
| Haiku 4.5 | $0.00010 | $0.00138 |
Grade A, and why
po-release-notes 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes Generator
Purpose
Release notes are not a commit log. Stakeholders and customers do not care which service was refactored — they care what they can do now that they couldn't do before. This skill reads the Sprint's completed work items and translates them into outcomes, grouped by theme, in language the audience actually understands.
Tool detection
- Check for active
mcp__azure-devops__*tools →$PM_TOOL = ado - Check for active
mcp__jira__*tools →$PM_TOOL = jira - If neither →
$PM_TOOL = manual
Step 1 — Identify the Sprint and audience
Ask: "Which Sprint are we writing release notes for? And who is the audience — customers, internal stakeholders, or both?"
| Audience | Tone | Detail level |
|---|---|---|
| Customers / end users | Plain language, benefit-focused | Feature outcomes only; no internal jargon |
| Internal stakeholders | Business language, outcome + context | Feature outcomes plus metrics/context |
| Technical stakeholders | More detail allowed | May include architecture changes, migrations |
Store as $SPRINT and $AUDIENCE.
Step 2 — Fetch completed work items
- ADO: use
wit_get_work_items_for_iterationfiltered to Done/Closed state, or usewit_query_by_wiqlfor the iteration. Read title, description, acceptance criteria, and type (Story, Bug, Task, Feature). - Jira: use sprint reporting tools to list resolved issues. Read summary, description, issue type, and fix version.
- Manual: ask "Paste the list of completed items — title, type, and a one-line description is enough."
Exclude purely technical work items (infrastructure tasks, pipeline fixes, dependency bumps) unless they have user-visible impact. When in doubt, ask the PO.
Step 3 — Group and categorise
Before writing, cluster the completed items into meaningful themes. Good themes are user-facing capability areas, not technical layers.
Good groupings:
- "Reporting" — items related to dashboards, exports, data views
- "Notifications" — items related to alerts, emails, push
- "Performance & reliability" — items that improved speed or fixed errors users experienced
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 · 137 lines · 103 tokens per session scan A 43f287469867
po-release-notes is a skill published in the GitHub repository abrahamFerga/scrum-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 103 tokens to every session and 1,378 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 skills, from other repositories
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
release-notes
Draft short release notes from a list of changes. Use when the user asks for changelogs, release notes, or a concise product update.
changelog
Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
release-notes
Create release notes for a new version tag. Gathers all commits, PRs, issues fixed, and breaking changes since a previous release. Creates the release notes markdown file, tags the repo, and pushes. Asks the user to confirm the base version to diff against.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.