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 atman-33/workhub --skill create-release-notesgit clone --depth 1 https://github.com/atman-33/workhubWrote 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/atman-33/workhub/create-release-notes)<a href="https://agentmods.dev/skills/atman-33/workhub/create-release-notes"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/create-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/atman-33/workhub/create-release-notes"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/create-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.00071 | $0.00663 |
| Opus 5.5 | $0.00028 | $0.00265 |
| Sonnet 5.5 | $0.00014 | $0.00133 |
| Haiku 4.5 | $0.00007 | $0.00066 |
Grade A, and why
create-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 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Release Notes
Release notes are for users of the software, not its developers — that distinction drives every step. A developer changelog (exhaustive, technical, commit-shaped) belongs to whatever release procedure the repository itself defines; this skill produces the announcement.
Steps
-
Determine the range. Default: latest tag →
HEAD(git describe --tags --abbrev=0). The user's explicit range or tag pair overrides. If no tag exists, ask what "since the last release" means here. -
Collect the changes.
git log <from>..<to> --pretty='%h %s%n%b'. Where commits are thin, enrich from merged PR titles/bodies (gh pr list --state merged --search <sha>— best-effort; skip silently ifghis unavailable). -
Filter for user visibility. Keep what a user can see or feel: features, fixes to behavior, performance, breaking changes, deprecations. Drop refactors, CI, tests, docs-tooling, dependency bumps — unless one has a user-visible consequence (e.g. a dependency bump that fixes a vulnerability), in which case describe the consequence, not the bump.
- Completion criterion: every commit in the range is either represented in a note or consciously dropped as internal — not silently lost.
-
Write the notes. In the language the release audience reads (ask if unclear). Rules:
- Lead with the highlights: 1–3 sentences on what this release is about.
- Sections in impact order: Breaking changes (with migration steps) → New → Improved → Fixed.
- Each item names the user benefit, not the implementation ("Search now matches partial words", not "Refactored tokenizer").
- No commit hashes or internal ticket ids in the body; keep a collapsed "full changelog" link/line at the end instead.
-
Deliver. Show the draft in chat. If the user wants a file, write where they say (convention:
docs/releases/<version>.md); if they want it on a GitHub release,gh release create <tag> --notes-file <file>(orgh release edit) — confirm before creating anything public.
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 · 54 lines · 71 tokens per session scan A 69c61141d80a
create-release-notes is a skill published in the GitHub repository atman-33/workhub (3 stars, last pushed 2d ago), licensed MIT. It adds 71 tokens to every session and 663 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
aetox-deploy
ก่อนปล่อยของและตอนเกิดเหตุ, checklist ก่อน deploy (migration, feature flag, rollback trigger, ยืนยัน CI), incident response (เกณฑ์ SEV1-4, สื่อสารระหว่างเหตุ, เขียน postmortem) และ git workflow ปลอดภัย (แยกงานด้วย worktree, ปิด branch ให้จบสะอาด) ทริกด้วย "จะ deploy", "production ล่ม", "ปิดงานยังไง".
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).