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/talayash/agentrium/changeloggit clone --depth 1 https://github.com/talayash/agentriumWhat 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 | $0.00000 | $0.00233 |
| Opus 5 | $0.00000 | $0.00117 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00023 |
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 3d 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
Generate changelog
Generate a changelog for version $ARGUMENTS by analyzing git history.
Steps
- Find the previous version tag using
git describe --tags --abbrev=0 HEAD^orgit tag --sort=-version:refname - Get all commits since that tag:
git log {previous_tag}..HEAD --oneline - For each commit, read the message and categorize it
Categories
Group changes into these sections (omit empty sections):
- New Features - New functionality added
- Bug Fixes - Issues resolved
- Improvements - Enhancements to existing features
- Internal - Refactoring, dependency updates, CI changes
Output format
## What's New in v{VERSION}
### New Features
- Description of feature (#PR if available)
### Bug Fixes
- Description of fix (#PR if available)
### Improvements
- Description of improvement (#PR if available)
Present the changelog to the user for review. If they approve, offer to copy it for use in a GitHub Release description.
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.
- 3d ago First seen · 36 lines · 0 tokens per session scan A 26b721cad648
changelog is a command published in the GitHub repository talayash/agentrium (39 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 233 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
release
(dev-only) release maintainer harness — MoAI-ADK production release (Enhanced GitHub Flow, scripts/release.sh + GoReleaser). NOT distributed to user projects.
celebrate
You are celebrating a project milestone! Follow these steps to create a new release.
bump
Bump Claudepot version numbers in lock-step across Cargo.toml, Cargo.lock, package.json, src-tauri/tauri.conf.json, README.md, the web install page, and stub a CHANGELOG section. Runs a quality gate first. Does not commit — leaves changes for review, and documents the tag/push path that follows.
release
Создать релиз фреймворка Claude Code Starter.
gsd:complete-milestone
Archive completed milestone and prepare for next version.
review-renovate
Review and merge renovate PRs with automerge configuration updates.