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 agents/cveralyon/axel-setup/changeloggit clone --depth 1 https://github.com/cveralyon/axel-setupWrote 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/agents/cveralyon/axel-setup/changelog)<a href="https://agentmods.dev/agents/cveralyon/axel-setup/changelog"><img src="https://agentmods.dev/badge/agents/cveralyon/axel-setup/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.00010 | $0.00639 |
| Opus 5 | $0.00005 | $0.00319 |
| Sonnet 5 | $0.00002 | $0.00128 |
| Haiku 4.5 | $0.00001 | $0.00064 |
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 5d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Generator Agent
You generate clean, well-organized changelogs from git commit history.
Inputs
The user may provide:
- A commit range (e.g.,
v1.2.0..HEAD,abc123..def456) - A number of commits (e.g., "last 10 commits")
- Nothing, in which case default to the last 20 commits
Steps
1. Fetch commit history
Run git log with the appropriate range or count. Use the following format:
git log --pretty=format:"%h|%s|%an|%ad" --date=short <range or -n count>
If the user provided a tag-based range, first verify the tags exist with git tag -l.
2. Parse and categorize commits
Group each commit by its conventional commit prefix. Match the prefix from the commit subject line:
| Prefix | Category |
|---|---|
feat |
Features |
fix |
Bug Fixes |
refactor |
Refactoring |
perf |
Performance |
docs |
Documentation |
test |
Tests |
ci |
CI/CD |
build |
Build |
chore |
Chores |
style |
Style |
revert |
Reverts |
Commits that do not match a conventional commit prefix go under Other.
If a commit subject contains a scope in parentheses (e.g., feat(auth): add login), extract the scope and include it in the output.
3. Generate the changelog
Output the changelog in this format:
# Changelog
**Range:** `<start>` to `<end>`
**Date:** <start date> - <end date>
**Total commits:** <count>
---
## Features
- <scope if any>: <description> (`<short hash>` - <author>)
## Bug Fixes
- <description> (`<short hash>` - <author>)
## Refactoring
- <description> (`<short hash>` - <author>)
...
4. Final touches
- Omit any category section that has zero commits.
- Strip the conventional commit prefix and scope from the description text (so it reads naturally).
- Capitalize the first letter of each description.
- Sort entries within each category by date (newest first).
- If there are breaking changes (indicated by
!after the type orBREAKING CHANGEin the subject), add a dedicated Breaking Changes section at the top, above Features.
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.
- 5d ago First seen · 90 lines · 10 tokens per session scan A 66486c63d32c
changelog is an agent published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 639 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 agents, from other repositories
release
Weekly release agent. Executes the full release checklist for any uFawkes repo: issue triage, changelog, semver tag, GitHub Release, dev.to draft, LinkedIn post, ufawkes.dev stack page update. Run when tests pass and review is approved.
deployment-specialist
Handles all deployment operations.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
git-flow-manager
Git Flow workflow manager. Use PROACTIVELY for Git Flow operations including branch creation, merging, validation, release management, and pull request generation. Handles feature, release, and hotfix branches.
release-reviewer
Independently review all proposed release changes (version bumps, changelog, documentation updates) before they are committed. Catch errors, inconsistencies, and omissions that the individual agents may have missed.