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 reem-sab/tech-writer-prompts --skill release-notesgit clone --depth 1 https://github.com/reem-sab/tech-writer-promptsWrote 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/reem-sab/tech-writer-prompts/release-notes)<a href="https://agentmods.dev/skills/reem-sab/tech-writer-prompts/release-notes"><img src="https://agentmods.dev/badge/skills/reem-sab/tech-writer-prompts/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/reem-sab/tech-writer-prompts/release-notes"><img src="https://agentmods.dev/badge/skills/reem-sab/tech-writer-prompts/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.00091 | $0.00751 |
| Opus 5 | $0.00046 | $0.00376 |
| Sonnet 5 | $0.00018 | $0.00150 |
| Haiku 4.5 | $0.00009 | $0.00075 |
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 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes
Turns a raw commit list or internal changelog into customer-facing release notes grouped into Breaking Changes, New, and Fixed, plus a one-line support-team summary you can paste straight into a ticket reply.
Inputs
{{CHANGES}}: A commit list, PR titles, or an internal changelog for the release.
How to apply
Substitute each {{PLACEHOLDER}} above with the user's actual content, then
follow the prompt below exactly — including its output format and its stated
limits.
You are turning an internal commit list or changelog into release notes for customers, written from the perspective of someone using the product — not someone who wrote the code. Translate implementation language into effect language: not "refactored the rate limiter," but what a user of the API would actually notice, if anything.
If a change has no user-visible effect (internal refactors, test-only changes, dependency bumps with no behavior change), leave it out of the notes entirely — don't manufacture a customer-facing line for something no customer would notice. It's fine for the notes to be shorter than the input list.
Grouping
Sort every user-visible change into exactly one of these three groups:
- Breaking Changes — anything that requires the customer to change their own code, config, or integration to keep working.
- New — new capability that wasn't possible before.
- Fixed — previously broken or incorrect behavior that now works as documented.
If a change is ambiguous between New and Fixed (e.g. a bug fix that also changes behavior customers may have relied on), put it under Breaking Changes instead — when in doubt, over-warn rather than under-warn.
Output format
## Support summary
<one sentence, written so a support agent could paste it directly into a
reply to a customer asking "what changed in this release." State the
single most impactful thing in this release, or "No customer-facing
changes in this release." if the notes are empty.>
## Breaking Changes
- <item, or "None in this release.">
## New
- <item, or "None in this release.">
## Fixed
- <item, or "None in this release.">
What ships with it
4 files 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.
- 9d ago First seen · 92 lines · 91 tokens per session scan A e3db4ad06e2c
release-notes is a skill published in the GitHub repository reem-sab/tech-writer-prompts (4 stars, last pushed 10d ago), licensed MIT. It adds 91 tokens to every session and 751 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-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.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.