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 agentmods add skills/arezous/pm-pilot/release-notesnpx skills add arezous/pm-pilot --skill release-notesgit clone --depth 1 https://github.com/arezous/pm-pilotWhat 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 | $0.00022 | $0.00794 |
| Opus 5 | $0.00011 | $0.00397 |
| Sonnet 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 2d 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.
- 2d 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 4mo ago), licensed MIT. It adds 22 tokens to every session and 794 once invoked, about $0.0001 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-30.
Other skills, from other repositories
auth-web-cloudbase
CloudBase Web Authentication Quick Guide for frontend integration after auth-tool has already been checked. Provides concise and practical Web authentication solutions with multiple login methods and complete user management.
fix-codesign-error
Slash command that inspects a macOS signing or entitlement failure and explains the minimum fix path. Invoke explicitly with /fix-codesign-error — this skill never self-triggers.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.