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.
git clone --depth 1 https://github.com/ParkerM2/create-claude-workflowWrote 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/parkerm2/create-claude-workflow/generate-changelog)<a href="https://agentmods.dev/commands/parkerm2/create-claude-workflow/generate-changelog"><img src="https://agentmods.dev/badge/commands/parkerm2/create-claude-workflow/generate-changelog.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.00016 | $0.02978 |
| Opus 5 | $0.00008 | $0.01489 |
| Sonnet 5 | $0.00003 | $0.00596 |
| Haiku 4.5 | $0.00002 | $0.00298 |
Grade A, and why
generate-changelog scanned grade A with 1 finding 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 6d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
const tags = execSync("git tag --sort=-version:refname --list 'v*' | head -20") How it starts
The opening of the file, as written. The whole thing — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automated Changelog Generation
Generates a production-ready changelog by aggregating merged PRs since the last release/tag. Auto-classifies entries by type (features, fixes, breaking changes, dependencies). Outputs markdown and optionally publishes to GitHub Release and Slack.
Usage
/generate-changelog [--from <tag>] [--to <ref>] [--github-release] [--slack] [--file <path>] [--format keep-a-changelog]
--from <tag>: Start from git tag (defaults to last tag)--to <ref>: End at git ref (defaults to HEAD)--github-release: Create GitHub Release with changelog--slack: Post summary to Slack channel--file <path>: Append changelog to file (CHANGELOG.md by default)--format: Output format (keep-a-changelog, simple)
Workflow
Phase 1: Detect Version Range
Identifies commit range between last release and HEAD.
// Detect last git tag
let fromRef = null;
try {
const tags = execSync("git tag --sort=-version:refname --list 'v*' | head -20")
.toString()
.trim()
.split("\n")
.filter(t => t);
if (tags.length === 0) {
fromRef = execSync("git rev-list --all | tail -1").toString().trim();
console.log(`ℹ No tags found; scanning from first commit`);
} else {
fromRef = tags[0];
console.log(`✓ Last release: ${fromRef}`);
}
} catch (err) {
console.error(`ERROR: Failed to detect git tags: ${err.message}`);
return gracefulFailure("Unable to detect version range; specify --from manually");
}
const toRef = argv.to || "HEAD";
// Verify range is valid
try {
const logOutput = execSync(`git log --oneline ${fromRef}..${toRef}`);
const commitCount = logOutput.toString().split("\n").filter(l => l).length;
console.log(`✓ Commit range: ${fromRef}..${toRef} (${commitCount} commits)`);
} catch (err) {
console.error(`ERROR: Invalid git range ${fromRef}..${toRef}`);
return gracefulFailure("Unable to determine changelog range");
}
Graceful degradation: If no tags, scan from first commit; allow manual range specification.
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.
- 6d ago First seen · 406 lines · 16 tokens per session scan A bb07738652cb
generate-changelog is a command published in the GitHub repository ParkerM2/create-claude-workflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 2,978 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
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.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.