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 berkcangumusisik/claude-code-practices --skill release-notesgit clone --depth 1 https://github.com/berkcangumusisik/claude-code-practicesWrote 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/berkcangumusisik/claude-code-practices/release-notes)<a href="https://agentmods.dev/skills/berkcangumusisik/claude-code-practices/release-notes"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/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/berkcangumusisik/claude-code-practices/release-notes"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/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.00014 | $0.00258 |
| Opus 5.5 | $0.00006 | $0.00103 |
| Sonnet 5.5 | $0.00003 | $0.00052 |
| Haiku 4.5 | $0.00001 | $0.00026 |
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 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
Generate Release Notes
Target version: $1 (or infer from package.json if not provided)
git tag --sort=-creatordate | head -5
git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges
Format
Group commits by type and write release notes in this structure:
## [version] - YYYY-MM-DD
### New Features
- ...
### Bug Fixes
- ...
### Performance
- ...
### Breaking Changes
- ...
### Internal
- ...
Rules:
- Skip chore/style/ci commits from user-facing sections
- Rewrite commit messages as user-friendly sentences (not "fix: null check" → "Fixed crash when user data is missing")
- If a commit references an issue/PR, link it:
([#123](...)) - BREAKING CHANGE footer entries go to Breaking Changes section
Output the final markdown, ready to paste into CHANGELOG.md or a GitHub release.
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 · 49 lines · 14 tokens per session scan A 4c02a3ae78ab
release-notes is a skill published in the GitHub repository berkcangumusisik/claude-code-practices (11 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 258 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
close
Update version tracking when finishing work on a skill bundle. Use when you're done editing a skill project and need to bump version headers, recompute manifest hashes, update the changelog, flag stale files, or prepare a commit message. Triggers on: "close the session", "update versions", "save the bundle", "I'm done…
hmem-release
Pre-publish checklist for hmem: skills synced, version bumped, tests green, nothing forgotten. Use before npm publish or when the user says 'release', 'publish', 'push a release', or 'neue Version'.
goal-release
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or…
omh-deploy-and-monitor
This is an OMH deploy-and-monitor workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
release
Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version.