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/el-feo/ai-context/changeloggit clone --depth 1 https://github.com/el-feo/ai-contextWrote 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/el-feo/ai-context/changelog)<a href="https://agentmods.dev/commands/el-feo/ai-context/changelog"><img src="https://agentmods.dev/badge/commands/el-feo/ai-context/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.00013 | $0.01640 |
| Opus 5 | $0.00006 | $0.00820 |
| Sonnet 5 | $0.00003 | $0.00328 |
| Haiku 4.5 | $0.00001 | $0.00164 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Default behavior:
- If no
fromprovided, uses the most recent tag - If no tags exist, uses the first commit
<usage_examples> Generate changelog since last tag:
/ghpm:changelog
Generate changelog between versions:
/ghpm:changelog from=v1.0.0 to=v1.1.0
Generate changelog to specific file:
/ghpm:changelog output=docs/CHANGELOG.md
Generate changelog from date:
/ghpm:changelog from=2024-01-01
</usage_examples>
<operating_rules>
- Parse PR titles and commit messages for conventional commit format
- Group changes by type (feat, fix, refactor, etc.)
- Include PR numbers and links
- Include contributor attribution
- Handle breaking changes specially (highlight at top)
- Preserve existing changelog content when appending </operating_rules>
<changelog_format>
Output Format
# Changelog
## [Unreleased] OR [vX.Y.Z] - YYYY-MM-DD
### Breaking Changes
- **scope:** description (#PR) @contributor
### Features
- **scope:** description (#PR) @contributor
### Bug Fixes
- **scope:** description (#PR) @contributor
### Performance
- **scope:** description (#PR) @contributor
### Code Refactoring
- **scope:** description (#PR) @contributor
### Documentation
- **scope:** description (#PR) @contributor
### Testing
- **scope:** description (#PR) @contributor
### Maintenance
- **scope:** description (#PR) @contributor
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 · 277 lines · 13 tokens per session scan A 0ff6178a5b15
changelog is a command published in the GitHub repository el-feo/ai-context (12 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 1,640 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-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.