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/caspian-sun/claude-code-workflow/releasegit clone --depth 1 https://github.com/Caspian-Sun/claude-code-workflowWhat 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.01065 |
| Opus 5 | $0.00000 | $0.00532 |
| Sonnet 5 | $0.00000 | $0.00213 |
| Haiku 4.5 | $0.00000 | $0.00106 |
Grade A, and why
release 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are now acting as a Release Engineer. Automatically generate a changelog from git history to assist with version releases.
Applicable Scenarios
- Before a version release — aggregate all changes since the last tag and generate a structured changelog
- Weekly report / iteration summary — summarize changes over a time range
- After PR merges — append to CHANGELOG.md
Input
| Input | Example | Behavior |
|---|---|---|
| No arguments | /release |
Auto-use range from the last git tag to HEAD |
| Version number | /release v1.2.0 |
Specify version; range same as above |
| Time range | /release --since 2026-04-01 |
Specified start date to HEAD |
| Two tags | /release v1.1.0..v1.2.0 |
Exact range |
Execution Flow
Step 1: Determine Range
- Read
git tag --sort=-creatordateto get the most recent tag - No tags → use commits from the last 30 days (or user-specified
--since) - After range is determined, output: "Changelog range:
<start>→HEAD, N commits total"
Step 2: Aggregate Commits
Read all commits in the range, parse by type(scope): description format:
git log <range> --pretty=format:"%H %s" --no-merges
Group by type:
| Type | Changelog Section | Notes |
|---|---|---|
| feat | New Features | New capabilities |
| fix | Bug Fixes | Bug fixes (includes [BUG-xxx] / [B00x] tags) |
| refactor | Refactoring | Code refactoring, no functional change |
| style | Style | UI / style adjustments |
| test | Tests | New or modified tests |
| docs | Documentation | Doc updates |
| chore | Other | Build / config / dependencies |
Step 3: Extract Traceability Info
For each commit, extract from the commit message and diff:
- Related PRD: grep for
@prdordocs/prds/references - Related task: grep for
@taskordocs/tasks/references - Related bug: grep for
[BUG-or[B0tags - Related PR: grep for
#<number>or match fromgh pr list --state merged - Affected module: infer from the scope field or file paths
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 · 116 lines · 0 tokens per session scan A e087369601b1
release is a command published in the GitHub repository Caspian-Sun/claude-code-workflow (10 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,065 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-31.
Other commands, from other repositories
create-manifest
Create a migration manifest for a new patch, beta, rc, or minor release based on commits since the previous release.
trellis-create-manifest
Create a migration manifest for a new patch/minor release based on commits since the last release.
release
Execute full version release — merge PRs, version bump, tag, GitHub Release, sync branches, cleanup.
ship
Deliver the increment. Then go live with a rollback you have run.
backfill
Find missing changelog entries from git commits since last tag.
changelog
Automatic changelog generation. Produces a structured changelog from commit history.