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/whchoi98/project-initWrote 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/whchoi98/project-init/generate-changelog)<a href="https://agentmods.dev/commands/whchoi98/project-init/generate-changelog"><img src="https://agentmods.dev/badge/commands/whchoi98/project-init/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.00022 | $0.01869 |
| Opus 5 | $0.00011 | $0.00934 |
| Sonnet 5 | $0.00004 | $0.00374 |
| Haiku 4.5 | $0.00002 | $0.00187 |
Grade A, and why
generate-changelog 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 7d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate CHANGELOG
Generate or update a bilingual (English/Korean) CHANGELOG.md based on git history, following Keep a Changelog and Semantic Versioning.
Step 1: Determine Operation Mode
Target: $ARGUMENTS
Three modes of operation:
- New: No existing
CHANGELOG.md— generate from full git tag history - Update unreleased: Argument is
unreleasedor empty — add new commits to[Unreleased]section - Release version: Argument is a version number (e.g.
1.2.0) — move[Unreleased]items to a new version section
ls CHANGELOG.md 2>/dev/null
Step 2: Gather Repository Information
GitHub URL:
git remote get-url origin 2>/dev/null
Convert SSH URL to HTTPS format for comparison links:
[email protected]:user/repo.git->https://github.com/user/repo
Version tags:
git tag --sort=-v:refname 2>/dev/null
Project name:
- Read from existing CHANGELOG.md title, or manifest file, or
CLAUDE.md
Step 3: Analyze Git History
For New CHANGELOG
Analyze the full tag history to build version entries:
# Get all tags sorted by version
git tag --sort=-v:refname
# For each consecutive tag pair, get commits between them
git log --oneline v1.0.0...v1.1.0
# Get the date of each tag
git log -1 --format=%aI v1.0.0
# Get commits before the first tag
git log --oneline v1.0.0
For Update (Unreleased)
Get commits since the last tag:
# Find the latest tag
git describe --tags --abbrev=0 2>/dev/null
# Get commits since last tag
git log --oneline $(git describe --tags --abbrev=0 2>/dev/null)...HEAD 2>/dev/null
# If no tags exist, get recent commits
git log --oneline -20
For Release
Read existing CHANGELOG.md and move [Unreleased] content to the new version heading.
Step 4: Categorize Changes
Classify each commit into the 6 standard categories based on commit message patterns:
| Commit Pattern | Category |
|---|---|
feat:, feature:, add: |
Added |
change:, update:, refactor: (user-facing) |
Changed |
deprecate: |
Deprecated |
remove:, delete: |
Removed |
fix:, bugfix:, hotfix: |
Fixed |
security:, vuln: |
Security |
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.
- 7d ago First seen · 214 lines · 22 tokens per session scan A e4d800dab075
generate-changelog is a command published in the GitHub repository whchoi98/project-init (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,869 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
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.