Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ratel-ai/ratelnpx agentmods add skills/ratel-ai/ratel/changelogWrote 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/ratel-ai/ratel/changelog)<a href="https://agentmods.dev/skills/ratel-ai/ratel/changelog"><img src="https://agentmods.dev/badge/skills/ratel-ai/ratel/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/ratel-ai/ratel/changelog"><img src="https://agentmods.dev/badge/skills/ratel-ai/ratel/changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00074 | $0.01696 |
| Opus 5 | $0.00037 | $0.00848 |
| Sonnet 5 | $0.00015 | $0.00339 |
| Haiku 4.5 | $0.00007 | $0.00170 |
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 10d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/changelog
Updates a release unit's CHANGELOG.md in preparation for tagging it. Ratel releases
per unit (ADR-0008): each unit ships on its own tag (<prefix>-v*) at its own version.
For workflow-wired units, .github/workflows/release.yml rejects a tag whose unit CHANGELOG
doesn't contain the version being released. vercel-ai-sdk is temporarily published
manually via scripts/publish-rc.sh; still run this skill before its tag even though the
workflow gate does not cover it yet.
Run it once per unit you're releasing.
Release units it touches
The units and their manifests/CHANGELOGs live in one registry —
scripts/release-units.mjs — which every release tool reads. Run node scripts/release-units.mjs --list
for the authoritative set; the current eight units are:
| Unit | Registry | CHANGELOG path |
|---|---|---|
core |
ratel-ai-core (crates.io) |
src/core/CHANGELOG.md |
sdk-ts |
@ratel-ai/sdk (npm) |
src/sdk/ts/CHANGELOG.md |
sdk-py |
ratel-ai (PyPI) |
src/sdk/python/CHANGELOG.md |
telemetry-core |
ratel-ai-telemetry (crates.io) |
src/telemetry/core/CHANGELOG.md |
telemetry-ts |
@ratel-ai/telemetry (npm) |
src/telemetry/ts/CHANGELOG.md |
telemetry-py |
ratel-ai-telemetry (PyPI) |
src/telemetry/python/CHANGELOG.md |
vercel-ai-sdk |
@ratel-ai/vercel-ai-sdk (npm) |
src/adapters/ts-vercel-ai-sdk/CHANGELOG.md |
mastra |
@ratel-ai/mastra (npm) |
src/adapters/ts-mastra/CHANGELOG.md |
@ratel-ai/mcp-server lives in ratel-ai/ratel-mcp and maintains its own CHANGELOG there.
Procedure
1. Pick the unit and read its version
If the user hasn't named the unit, run node scripts/releasable.mjs — it lists which
units have commits since their last release tag. Pick the unit $UNIT being released.
Read its canonical version:
node scripts/release-units.mjs --version "$UNIT" # -> $TARGET
If the user supplies a different version explicitly, prefer that and warn them the working tree disagrees.
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.
- 10d ago First seen · 143 lines · 74 tokens per session scan A a0cd824ac5b3
changelog is a skill published in the GitHub repository ratel-ai/ratel (434 stars, last pushed 2d ago), licensed MIT. It adds 74 tokens to every session and 1,696 once invoked, about $0.0004 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 skills, from other repositories
changelog
Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.
ship
Enter the Ship phase of CocoBrew. Reads review.md approval, generates structured commit, creates semantic version tag, optionally creates PR via gh CLI, and records deployment details. Requires approved review.
parallel-pr-review
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
release-management
Automates GitHub releases with semantic versioning, changelog generation from merged PRs, and gh CLI integration. Supports draft, prerelease, and standard release workflows with task-tracked multi-phase execution. Use when creating releases, tagging versions, or publishing changelogs.
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.