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 agentmods add commands/centminmod/my-claude-code-setup/create-release-notegit clone --depth 1 https://github.com/centminmod/my-claude-code-setupWhat 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 | $0.00000 | $0.03929 |
| Opus 5 | $0.00000 | $0.01965 |
| Sonnet 5 | $0.00000 | $0.00786 |
| Haiku 4.5 | $0.00000 | $0.00393 |
Grade A, and why
create-release-note 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 2d 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 — 535 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Note Generator
Generate comprehensive release documentation from recent commits, producing two distinct outputs: a customer-facing release note and a technical engineering note.
Interactive Workflow
When this command is triggered, DO NOT immediately generate release notes. Instead, present the user with two options:
Mode Selection Prompt
Present this to the user:
I can generate release notes in two ways:
**Mode 1: By Commit Count**
Generate notes for the last N commits (specify number or use default 10)
→ Quick generation when you know the commit count
**Mode 2: By Commit Hash Range (i.e. Last 24/48/72 Hours)**
Show all commits from the last 24/48/72 hours, then you select a starting commit
→ Precise control when you want to review recent commits first
Which mode would you like?
1. Commit count (provide number or use default)
2. Commit hash selection (show last 24/48/72 hours)
You can also provide an argument directly: /create-release-note 20
Mode 1: By Commit Count
Usage
/create-release-note # Triggers mode selection
/create-release-note 20 # Directly uses Mode 1 with 20 commits
/create-release-note 50 # Directly uses Mode 1 with 50 commits
Process
- If
$ARGUMENTSis provided, use it as commit count - If no
$ARGUMENTS, ask user for commit count or default to 10 - Set:
COMMIT_COUNT="${ARGUMENTS:-10}" - Generate release notes immediately
Mode 2: By Commit Hash Range
Workflow
When user selects Mode 2, follow this process:
Step 1: Retrieve Last 24 Hours of Commits
git log --since="24 hours ago" --pretty=format:"%h|%ai|%an|%s" --reverse
Step 2: Present Commits to User
Format the output as a numbered list for easy selection:
Commits from the last 24 hours (oldest to newest):
1. a3f7e821 | 2025-10-15 09:23:45 | Alice Smith | Add OAuth provider configuration
2. b4c8f932 | 2025-10-15 10:15:22 | Bob Jones | Implement token refresh flow
3. c5d9e043 | 2025-10-15 11:42:18 | Alice Smith | Add provider UI components
4. d6e1f154 | 2025-10-15 13:08:33 | Carol White | Database connection pooling
5. e7f2g265 | 2025-10-15 14:55:47 | Alice Smith | Query optimization middleware
6. f8g3h376 | 2025-10-15 16:20:12 | Bob Jones | Dark mode CSS variables
7. g9h4i487 | 2025-10-15 17:10:55 | Carol White | Theme switching logic
8. h0i5j598 | 2025-10-16 08:45:29 | Alice Smith | Error boundary implementation
Please provide the starting commit hash (8 characters) or number.
Release notes will be generated from your selection to HEAD (most recent).
Example: "a3f7e821" or "1" will generate notes for commits 1-8
Example: "d6e1f154" or "4" will generate notes for commits 4-8
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.
- 2d ago First seen · 535 lines · 0 tokens per session scan A 70b145fb96f3
create-release-note is a command published in the GitHub repository centminmod/my-claude-code-setup (2,614 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,929 tokens. 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-30.
Other commands, from other repositories
generate-changelog
Generate a changelog from git history, grouping commits by type and version.
write-changelog
Generate a detailed changelog entry from git history and merged PRs.
versioning
Universal version file discovery and sync. Works with any project structure.
release
Command "release" from khuynh22/mcp-wireshark, covering how it works, what to tell the user, if no label is added and manual fallback.
claudikins-kernel:ship
Final shipping gate. PR creation, documentation updates, and merge with human approval.
release
Format, bump version, commit and push plugin release. Ship it.