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 skills add ekline-io/ekline-docs-skills --skill changeloggit clone --depth 1 https://github.com/ekline-io/ekline-docs-skillsWrote 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/skills/ekline-io/ekline-docs-skills/changelog)<a href="https://agentmods.dev/skills/ekline-io/ekline-docs-skills/changelog"><img src="https://agentmods.dev/badge/skills/ekline-io/ekline-docs-skills/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/skills/ekline-io/ekline-docs-skills/changelog"><img src="https://agentmods.dev/badge/skills/ekline-io/ekline-docs-skills/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.00059 | $0.00683 |
| Opus 5 | $0.00030 | $0.00342 |
| Sonnet 5 | $0.00012 | $0.00137 |
| Haiku 4.5 | $0.00006 | $0.00068 |
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 11d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate changelog
Run the helper script to parse git history, then present and optionally write the results.
Inputs
$ARGUMENTS— optional version tag or commit range (e.g.,v1.3.0,v1.2.0..v1.3.0,HEAD~20..HEAD)
Steps
1. Run the helper script
python scripts/parse_commits.py $ARGUMENTS
Capture the JSON output. The script handles range detection, commit parsing, conventional commit classification, keyword heuristics, PR/issue extraction, and deduplication.
Max 200 commits per run.
2. Handle errors
If the JSON contains an error field:
not_a_git_repo— tell user to run from inside a git repositoryno_commits— tell user no commits were found in the given range, suggest a different range
Stop here on error.
3. Present the changelog entry
Using the categories object from the JSON, format a Keep a Changelog entry:
## [Unreleased] - YYYY-MM-DD
### Breaking Changes
- {text from entries}
### Added
- {text from entries}
### Changed
- {text from entries}
### Fixed
- {text from entries}
### Removed
- {text from entries}
### Security
- {text from entries}
Only include categories that have entries. Use the text field from each entry directly — the script already formats entries with imperative mood and PR references.
Show the user:
- Number of commits analyzed (
total_commits_analyzed) - Number of entries generated (
total_changelog_entries) - Number skipped as internal (
total_skipped) - The full formatted entry
4. Ask the user
Ask whether they want to:
- Write the entry to
CHANGELOG.md - Just see the output (done)
5. Write to CHANGELOG.md
If the user wants to write:
If CHANGELOG.md exists:
- Read it with the Read tool
- Insert the new entry after the file header (before the first
## [line) - Preserve all existing content
If CHANGELOG.md does not exist:
- Create it with the standard header:
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
{generated entry here}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 109 lines · 59 tokens per session scan A 9c9d8b06a88d
changelog is a skill published in the GitHub repository ekline-io/ekline-docs-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 683 once invoked, about $0.0003 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 skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.