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 aaronjmars/aeon-agent --skill changeloggit clone --depth 1 https://github.com/aaronjmars/aeon-agentWrote 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/aaronjmars/aeon-agent/changelog)<a href="https://agentmods.dev/skills/aaronjmars/aeon-agent/changelog"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/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/aaronjmars/aeon-agent/changelog"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/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.00047 | $0.05817 |
| Opus 5 | $0.00023 | $0.02908 |
| Sonnet 5 | $0.00009 | $0.01163 |
| Haiku 4.5 | $0.00005 | $0.00582 |
Grade C, and why
changelog scanned grade C with 2 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$WORK_DIR" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
The window is the primary filter; the published-PR dedup in step B.2 is the idempotency guard against overlap and re-runs. Sandbox: if `gh api` fails transiently, retry once. Never use `curl` for the GitHub API — `gh` ha This is a copy
100% identical to changelog — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — Selects the mode and target:
- empty → in-repo changelog across every repo in
memory/watched-repos.md.owner/repo(bare slug) → in-repo changelog for that single repo only.push-to:owner/website-repo→ cross-repo mode: publish the product's merged PRs as a changelog PR onowner/website-repo(product repo comes frommemory/docs-sync.md).owner/product->owner/website(arrow form) → cross-repo mode with both product and website repos given explicitly.
Why this skill exists
A changelog is not a commit log. Raw commit dumps grouped by conventional prefix are the noise anti-pattern — users can't tell what matters. This skill produces a Keep a Changelog-style summary: categorized, plain-English, breaking changes surfaced, internal churn filtered out. It runs in two modes: in-repo (write the article into this repo) or push-to (open a changelog PR on a separate marketing/docs website repo).
0. Preamble — read memory and parse the selector
Read memory/MEMORY.md and the last 3 days of memory/logs/ for context (prior runs, known issues). Before notifying, drop anything already reported in that window.
Parse ${var} to pick the branch:
${var} |
Branch | Target |
|---|---|---|
| empty | A — in-repo | all repos in memory/watched-repos.md |
owner/repo (no push-to:, no ->) |
A — in-repo | only that repo |
push-to:owner/website-repo |
B — push-to | website = owner/website-repo; product = config product_repo |
owner/product->owner/website |
B — push-to | product = owner/product; website = owner/website |
Disambiguation: a push-to: prefix or a -> arrow selects Branch B; anything else (empty or a bare owner/repo) selects Branch A. Then jump to the matching branch below.
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.
- 4d ago Changed · +4 lines 963c9d733523
- 9d ago First seen · 406 lines · 47 tokens per session scan C 48ae451ff50c
changelog is a skill published in the GitHub repository aaronjmars/aeon-agent (11 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 5,817 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). It is 100% identical to changelog, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
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.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.