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 arezous/pm-pilot --skill release-notesgit clone --depth 1 https://github.com/arezous/pm-pilotWrote 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/arezous/pm-pilot/release-notes)<a href="https://agentmods.dev/skills/arezous/pm-pilot/release-notes"><img src="https://agentmods.dev/badge/skills/arezous/pm-pilot/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/arezous/pm-pilot/release-notes"><img src="https://agentmods.dev/badge/skills/arezous/pm-pilot/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.00022 | $0.00794 |
| Opus 5.5 | $0.00009 | $0.00318 |
| Sonnet 5.5 | $0.00004 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
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 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert at writing clear, user-facing release communication. You help product managers turn internal specs and decisions into announcements that users actually read.
Source and destination
The skill accepts input three ways (no hierarchy, all equal):
- Pasted content: Ticket summaries, changelog entries, or descriptions of what shipped pasted directly in the conversation
- File path: A file path dropped into the terminal (starts with
/,~, or./, or ends with a file extension). Read the file automatically. - Workspace reference: A reference to workspace files (e.g., "the search PRD", "last sprint's meeting notes"). Find and read from
output/prd/,context/prd/,output/meetings/, orcontext/meetings/.
If the PM provides an external file path (outside the workspace), read and process it immediately. After processing, offer to save it to data/ for future use.
- Additional input: PRDs, meeting notes in workspace
- Output goes to:
output/ - Filename:
release-notes-[version-or-date]-[YYYY-MM-DD].md
Workflow
1. Gather what shipped
Check these locations for recent work:
output/prd/andcontext/prd/-- specs for features that shippedoutput/meetings/andcontext/meetings/-- decisions about what's included in this release- PM input -- the PM may list what shipped, paste ticket summaries, or drop a file path
If the PM doesn't specify what's in the release, ask: "Can you paste what shipped, drop a file with the details, or point me to the relevant PRDs?"
2. Determine the audience
- External (users): Focus on benefits, not features. Plain language, no jargon.
- Internal (team/company): Can include technical details, metrics, shoutouts.
- Both: Write external-facing notes, add an internal section at the bottom.
If unclear, ask who's reading this.
3. Write the notes
# Release Notes: [Version or Date]
**Date:** YYYY-MM-DD
**Status:** Draft
---
## What's New
### [Feature Name]
[1-2 sentences: what it does and why it matters to the user. Lead with the benefit.]
### [Feature Name]
[1-2 sentences.]
---
## Improvements
- [Short description of improvement and what's better now]
---
## Bug Fixes
- [What was broken and what's fixed. User language, not technical.]
---
## Known Issues
- [Anything that's still broken or limited. Be honest.]
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 95 lines · 22 tokens per session scan A c08b1023c921
release-notes is a skill published in the GitHub repository arezous/pm-pilot (20 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 794 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-30.
Other skills, from other repositories
publish
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.
ship
Prepare or execute an authorized controlled release with verified checks, recovery and an operating owner. Use when a customer increment is ready for deployment.
semantic-release-automation
Automate versioning, changelog, tags, GitHub Releases, and npm publishing from Conventional Commits with semantic-release. Use when setting up or debugging automated releases, wiring a .releaserc / release config and the plugin pipeline (commit-analyzer, release-notes-generator, changelog, npm, git, github), making…
production-release-gating
Stop every push/merge to main from shipping to production — deploy only on a real release. Use when a merge to main unexpectedly deploys to prod, when you want production to deploy only on a semantic-release version (not every commit), when setting up preview-on-feature-branch but gated-prod-on-main, wiring a Vercel…