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/coralogix/canopy/changelog-draftgit clone --depth 1 https://github.com/coralogix/canopyWrote 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/coralogix/canopy/changelog-draft)<a href="https://agentmods.dev/commands/coralogix/canopy/changelog-draft"><img src="https://agentmods.dev/badge/commands/coralogix/canopy/changelog-draft.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.00000 | $0.00360 |
| Opus 5 | $0.00000 | $0.00180 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
changelog-draft 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 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.
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.
What it actually says
/changelog-draft
Generate a changelog entry from git history since the last tag (or a specified range).
Steps
- Find the most recent git tag:
git describe --tags --abbrev=0 - Get commits since that tag:
git log <tag>..HEAD --oneline --no-merges - For each commit message, classify it:
- Added — new features, new commands, new files
- Changed — modified behavior, refactors, updates
- Fixed — bug fixes, error corrections
- Removed — deleted features, removed files
- Security — security fixes or vulnerability patches
- Internal — CI changes, dependency bumps, test additions (include but de-emphasize)
- Write the entry in Keep a Changelog format using today's date and the next version if known, or
[Unreleased]. - Check if
CHANGELOG.mdexists. If so, show the new entry formatted to insert at the top.
Output Format
## [Unreleased] - YYYY-MM-DD
### Added
- [description] ([commit hash])
### Fixed
- [description] ([commit hash])
### Changed
- [description] ([commit hash])
Rules
- Exclude merge commits and bot commits (e.g., "Merge pull request #...")
- Rewrite commit messages into user-facing language: "fix null pointer in auth middleware" → "Fixed authentication crash when user token is missing"
- If there are no commits since the last tag, say so
- If there are more than 20 commits, focus on user-facing changes and summarize internal changes as a single line
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 · 40 lines · 0 tokens per session scan A 64a73c308879
changelog-draft is a command published in the GitHub repository coralogix/canopy (89 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 360 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
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
Command "release-plan" from alisunstar/OpenSunstar, covering /rd:release-plan — 发布计划, 先读, 执行, 产物 and 人工确认.
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.