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/dokkabei97/forged-claude-code/release-notergit clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/commands/dokkabei97/forged-claude-code/release-noter)<a href="https://agentmods.dev/commands/dokkabei97/forged-claude-code/release-noter"><img src="https://agentmods.dev/badge/commands/dokkabei97/forged-claude-code/release-noter.svg" alt="Measured on agentmods" 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.00028 | $0.00734 |
| Opus 5 | $0.00014 | $0.00367 |
| Sonnet 5 | $0.00006 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
release-noter 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 5d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release-noter - Release Notes Generator
Triggers
- After merging a release branch
- Before publishing a product update
- For investor/board update communications
Usage
/release-noter
/release-noter --since v1.2.0
/release-noter --since 2026-02-01
/release-noter --audience users # Customer-facing
/release-noter --audience internal # Team-facing
/release-noter --audience investors # Business-focused
Behavioral Flow
Phase 1: Collect Changes
git log --oneline --since="[date]" --no-merges
git log --oneline v1.2.0..HEAD --no-merges
Phase 2: Categorize Changes
| Category | Icon | Git Patterns |
|---|---|---|
| New Features | ✨ | feat:, add:, new: |
| Improvements | 🔧 | improve:, enhance:, update: |
| Bug Fixes | 🐛 | fix:, bugfix:, patch: |
| Performance | ⚡ | perf:, optimize: |
| Security | 🔒 | security:, vuln: |
| Breaking Changes | ⚠️ | BREAKING:, breaking: |
Phase 3: Generate by Audience
For Users (customer-facing):
# What's New in v1.3.0
## ✨ New Features
- **[Feature Name]**: [Benefit-focused description in plain language]
- **[Feature Name]**: [What users can now do]
## 🔧 Improvements
- [Improvement in user-friendly terms]
## 🐛 Bug Fixes
- Fixed an issue where [user-visible problem]
## ⚠️ Breaking Changes
- [What changed and what users need to do]
For Internal Team:
# Release v1.3.0 — YYYY-MM-DD
## Summary
[N] features, [N] improvements, [N] bug fixes
## Changes
| Type | Description | PR | Author |
|------|------------|-----|--------|
| feat | [Technical description] | #123 | @dev |
## Migration Notes
- [Database changes]
- [Config changes]
- [Dependency updates]
For Investors:
# Product Update — [Month Year]
## Key Highlights
- Shipped [N] features that [business impact]
- [Metric] improved by [X]%
- [Customer/user milestone]
## What We Built
1. **[Feature]** — [Business value, not technical detail]
## What's Next
- [Upcoming priority with business rationale]
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.
- 5d ago First seen · 118 lines · 28 tokens per session scan A 28f63b653463
release-noter is a command published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 734 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes. Invoke with /create-pr.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release
Create a release branch, run changeset version, review changelog, and prepare PR.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.