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 uthumany/uthy-legacy-os --skill release-notesgit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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/uthumany/uthy-legacy-os/release-notes)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/release-notes"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/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/uthumany/uthy-legacy-os/release-notes"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/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.00032 | $0.00746 |
| Opus 5 | $0.00016 | $0.00373 |
| Sonnet 5 | $0.00006 | $0.00149 |
| Haiku 4.5 | $0.00003 | $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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes
Overview
Release notes are your product's public diary. Well-written notes inform users, build trust, and highlight the value of what you shipped. This skill covers writing for different audiences: end users, enterprise buyers, and internal teams.
When to Use
- You're shipping a new version of your product
- You want to communicate changes to users
- You need enterprise-grade release notes for compliance
- Don't use for: internal build descriptions (use commit messages), marketing announcements (use blog posts)
Instructions
1. Segment Your Audience
End Users (in-app or email):
- Focus on what's NEW and what's BETTER
- Use benefit-oriented language ("Now you can...")
- Screenshots and GIFs > text
- Friendly, conversational tone
Enterprise / Admin (admin dashboard):
- Include all changes (even minor ones)
- Add upgrade, migration, or configuration notes
- Document API changes, deprecations
- Professional, informative tone
Internal / Engineering (Slack, mailing list):
- Include technical details, gotchas
- Migration instructions, config changes
- Known issues and workarounds
- Honest, direct tone
2. Structure Each Entry
## [Version Number] - [Date]
### 🚀 New Features
- [Headline what's new] — [1-2 sentences on value]
### 🔧 Improvements
- [What changed and why it's better]
### 🐛 Bug Fixes
- [Problem] — [Fix] — [Effect]
### ⚠️ Known Issues
- [Issue] — [Workaround]
### 📦 Technical Notes (enterprise only)
- [Upgrade notes, config changes, API changes]
3. Writing Guidelines
- Start with the most important change — Users scan, they don't read
- Use active voice — "You can now..." not "An option to... has been added"
- Specify who benefits — "Team admins can now..." not "Improved admin panel"
- Link to docs — For complicated features, link to full documentation
- Acknowledge contributions — Thank beta testers, early adopters, or contributors
Sample Output
## v2.4.0 - June 4, 2026
### 🚀 New Features
- **Async team updates** — Share status updates without scheduling a meeting. Team members can post text, links, and screenshots that compile into a daily digest.
- **AI status summaries** — One-click summary of the week's updates (Enterprise feature)
### 🔧 Improvements
- **Faster search** — Results now load 3x faster with indexed search
- **Simplified onboarding** — New users can invite their team in 2 clicks instead of 5
### 🐛 Bug Fixes
- Fixed: Calendar sync showing incorrect timezone on Safari
- Fixed: Notification preferences not saving for team members with dots in email
### ⚠️ Known Issues
- Team dashboard may appear empty for accounts with 50+ projects. Refresh to reload.
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 · 98 lines · 32 tokens per session scan A 876c8f44b464
release-notes is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 746 once invoked, about $0.0002 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.