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 bmbouter/redhat-agents --skill release-notes-draftergit clone --depth 1 https://github.com/bmbouter/redhat-agentsWrote 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/bmbouter/redhat-agents/release-notes-drafter)<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/release-notes-drafter"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/release-notes-drafter/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/bmbouter/redhat-agents/release-notes-drafter"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/release-notes-drafter.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.00027 | $0.00426 |
| Opus 5.5 | $0.00011 | $0.00170 |
| Sonnet 5.5 | $0.00005 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
release-notes-drafter 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.
What it actually says
When to Use
At release time, or when the PM needs to communicate what shipped over a period.
Instructions
Read local/jira-workflow.md to understand statuses and epic conventions.
1. Define the release scope
Ask the PM:
- Time period or version: Since last release? Specific date range? Version number?
- Audience: Internal team? Customers? Public changelog?
- Format: Markdown? Confluence? Email?
2. Query closed work
project = <PROJECT> AND status = Closed AND status changed to Closed after "<start_date>" ORDER BY issuetype ASC, resolved DESC
Group by parent epic where possible.
3. Translate to user language
For each item:
- Rewrite the Jira summary from technical language to user-oriented language
- Focus on what the user can now do, not what code changed
- For bug fixes, describe what was broken and that it's now fixed
- Skip purely internal/infrastructure changes unless they affect users
4. Draft the release notes
## Release Notes — [Version / Date]
### New Features
- **[Feature name]**: [What users can now do]. ([EPIC-123])
### Improvements
- **[Improvement]**: [What got better and why it matters]. ([ISSUE-456])
### Bug Fixes
- Fixed an issue where [user-visible symptom]. ([ISSUE-789])
- Fixed [another issue]. ([ISSUE-012])
### Known Issues
- [Any known issues to call out]
5. Flag items for review
Mark any items where:
- The user impact is unclear from the ticket
- The change might need a migration note or breaking change warning
- The summary was too technical to translate confidently
Present to the PM for review. Iterate before publishing.
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 · 64 lines · 27 tokens per session scan A debc87fb57f4
release-notes-drafter is a skill published in the GitHub repository bmbouter/redhat-agents (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 426 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-31.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…