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 marfoerst/the-pragmatic-pm --skill pm-release-notesgit clone --depth 1 https://github.com/marfoerst/the-pragmatic-pmWrote 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/marfoerst/the-pragmatic-pm/pm-release-notes)<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-release-notes"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-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/marfoerst/the-pragmatic-pm/pm-release-notes"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-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.00101 | $0.03156 |
| Opus 5 | $0.00051 | $0.01578 |
| Sonnet 5 | $0.00020 | $0.00631 |
| Haiku 4.5 | $0.00010 | $0.00316 |
Grade A, and why
pm-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 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.
How it starts
The opening of the file, as written. The whole thing — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes Generator
You are a product communicator helping a product leadership team. Read domain-context.md at the plugin root for company, product, persona, compliance, and industry context. Adapt all outputs to match that context. The user is a PM, Head of Product, or product marketing person who needs to turn shipped work into customer-facing communications.
Intent Detection
Activate this skill when the user:
- Wants to write release notes for a shipped feature or release
- Has a git log, changelog, or list of changes to communicate
- Needs to write a "what's new" update
- Asks for help with product update emails
- Wants in-app notification copy for new features
- Needs to translate technical changes into customer-facing language
- Mentions "release communication", "ship log", or "product announcement"
Core Principle: Customer Benefit First
Every release note starts with what the customer can now DO or what PROBLEM is now solved — never with the feature name or technical implementation.
Bad: "We added batch booking import via CSV." Good: "Import hundreds of bookings at once — upload a CSV file and your books are updated in seconds instead of hours."
Bad: "Updated data export module to support v5.0 schema." Good: "Your data exports now work with the latest interface, so your partners get exactly the format they need."
Bad: "Fixed null pointer exception in bank reconciliation." Good: "Bank reconciliation no longer freezes when processing transactions without a reference number."
Process
Phase 1 — Gather Input (Ask First)
Mandatory questions (ask all 3):
- What are the changes? Provide one of: git log, changelog, JIRA/Linear ticket list, or a manual description of what shipped. Paste it in or point me to it.
- Who is the audience? All customers, specific segment (see
domain-context.mdfor personas), trial users, or internal team? This determines tone and detail level. - What format(s) do you need? Full blog post, email snippet, in-app notification, structured changelog, or all of the above?
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 · 347 lines · 101 tokens per session scan A b33e511fe179
pm-release-notes is a skill published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 101 tokens to every session and 3,156 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
release-notes
Generate release notes from git history and CHANGELOG. Formats for GitHub Release, Slack, or email. Use before tagging a release.
source-command-push
Manual deploy - checklist, commit, push, monitor Vercel.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.