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/gopherguides/gopher-aiWrote 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/gopherguides/gopher-ai/changelog)<a href="https://agentmods.dev/commands/gopherguides/gopher-ai/changelog"><img src="https://agentmods.dev/badge/commands/gopherguides/gopher-ai/changelog/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/gopherguides/gopher-ai/changelog"><img src="https://agentmods.dev/badge/commands/gopherguides/gopher-ai/changelog.svg" alt="Reviewed on agentmods" width="80" 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.00008 | $0.01518 |
| Opus 5.5 | $0.00003 | $0.00607 |
| Sonnet 5.5 | $0.00002 | $0.00304 |
| Haiku 4.5 | $0.00001 | $0.00152 |
Grade A, and why
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 1mo 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Latest tag: !
git describe --tags --abbrev=0 2>/dev/null || echo "No tags found" - Commits since last tag: !
TAG=\git describe --tags --abbrev=0 2>/dev/null || echo "HEAD~20"`; git log "$TAG"..HEAD --format="%h %s" 2>/dev/null | head -15 || echo "No commits found"` - Repository: !
basename \git rev-parse --show-toplevel 2>/dev/null` 2>/dev/null || echo "unknown"`
If $ARGUMENTS is empty or not provided:
Generate a changelog from commits since the last release tag.
Usage: /changelog [starting-point]
Examples:
/changelog- Since last tag/changelog v1.2.0- Since specific tag/changelog HEAD~50- Last 50 commits/changelog 2024-01-01- Since date
Workflow:
- Find the latest git tag
- Parse commits using Conventional Commits format
- Group by type (Added, Fixed, Changed, etc.)
- Generate Keep a Changelog formatted output
Proceed with commits since last tag.
If $ARGUMENTS is provided:
Generate a changelog from git commits since the specified starting point.
Configuration
- Since:
$ARGUMENTS(tag, commit ref, or date)
Steps
-
Identify Release Points
- Find the latest tag:
git describe --tags --abbrev=0 2>/dev/null || echo "" - If
$ARGUMENTSprovided, use as starting point - If no tags exist, use first commit or a reasonable limit (last 100 commits)
- Find the latest tag:
-
Gather Commits Run:
git log <since>..HEAD --format="%H|%s|%b|%an|%ae" --reverseFor each commit, extract:
- Hash (for linking)
- Subject line
- Body (for breaking changes, closes/fixes references)
- Author info
-
Parse Conventional Commits Categorize commits into Keep a Changelog sections:
Conventional Commit Changelog Section feat:,feature:Added fix:,bugfix:Fixed perf:Changed (Performance) refactor:Changed docs:Changed (Documentation) BREAKING CHANGE:Changed (Breaking) deprecate:Deprecated remove:Removed security:Security chore:,build:,ci:,test:(Skip or group as "Other")
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.
- 1mo ago Changed · +1 lines 18503f8b8528
- 1mo ago First seen · 192 lines · 8 tokens per session scan A 6ab57df81fac
changelog is a command published in the GitHub repository gopherguides/gopher-ai (21 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 1,518 once invoked, about $0.0000 per session on Opus 5.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-09-03.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or 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.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
ship
Ship is the operational release-prep flow for a connected project repo.