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 ClarentCinematics/Codex-Skills-for-Enterprise --skill release-notes-generatorgit clone --depth 1 https://github.com/ClarentCinematics/Codex-Skills-for-EnterpriseWrote 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/clarentcinematics/codex-skills-for-enterprise/release-notes-generator)<a href="https://agentmods.dev/skills/clarentcinematics/codex-skills-for-enterprise/release-notes-generator"><img src="https://agentmods.dev/badge/skills/clarentcinematics/codex-skills-for-enterprise/release-notes-generator/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/clarentcinematics/codex-skills-for-enterprise/release-notes-generator"><img src="https://agentmods.dev/badge/skills/clarentcinematics/codex-skills-for-enterprise/release-notes-generator.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.00060 | $0.00365 |
| Opus 5.5 | $0.00024 | $0.00146 |
| Sonnet 5.5 | $0.00012 | $0.00073 |
| Haiku 4.5 | $0.00006 | $0.00036 |
Grade A, and why
release-notes-generator 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
Release Notes Generator
Workflow
- Identify release scope, audience, product area, date range, and source artifacts.
- Group changes by user value, operational impact, bug fixes, breaking changes, and internal-only work.
- Translate technical changes into outcome-focused language appropriate for the audience.
- Preserve material caveats: migrations, feature flags, rollout limits, known issues, and support impact.
- Produce notes that can be used for customers, internal teams, support, or executives.
Output Standard
Use this structure by default:
- Release Summary: concise overview of the release.
- Highlights: highest-value user or business outcomes.
- Improvements: user-facing changes grouped by theme.
- Fixes: resolved issues with impact, not raw ticket noise.
- Breaking Changes / Migrations: required user or operator action.
- Known Issues: limitations, workarounds, and follow-up owner if known.
- Internal Notes: operational, support, rollout, or enablement details.
Rules
- Do not expose internal implementation details in customer-facing notes unless useful.
- Do not invent features, dates, ticket status, or customer impact.
- Mark uncertain release scope as
Not stated. - Separate external release notes from internal enablement notes.
References
Read references/release-note-patterns.md when the user asks for customer, executive, support, or developer-facing notes.
What ships with it
2 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.
- 1mo ago First seen · 38 lines · 60 tokens per session scan A b2b55606fa02
release-notes-generator is a skill published in the GitHub repository ClarentCinematics/Codex-Skills-for-Enterprise (2 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 365 once invoked, about $0.0002 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
antigravity-maintainer-batch-release
Run protected AAS maintainer sweeps, PR merge batches, resumable review, immutable distribution, Core checks, and scripted releases. Use for repository maintenance, main alignment, CLI/MCP/Workbench changes, or release work; not ordinary contribution tasks.
write-release-notes
Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to write, generate, or create release notes…
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…
skillshare-release
Prepare and review skillshare releases using the Release Please PR, verify the proposed version and changelog, inspect draft assets, and publish through the manual Publish Release workflow when explicitly authorized. Use when the user says "release", "prepare release", "cut a release", or asks to publish a new…