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/fxd0h/Axelera-Voyager-Local-Assistantnpx agentmods add skills/fxd0h/axelera-voyager-local-assistant/voyager-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/fxd0h/axelera-voyager-local-assistant/voyager-changelog)<a href="https://agentmods.dev/skills/fxd0h/axelera-voyager-local-assistant/voyager-changelog"><img src="https://agentmods.dev/badge/skills/fxd0h/axelera-voyager-local-assistant/voyager-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/fxd0h/axelera-voyager-local-assistant/voyager-changelog"><img src="https://agentmods.dev/badge/skills/fxd0h/axelera-voyager-local-assistant/voyager-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.00042 | $0.00503 |
| Opus 5 | $0.00021 | $0.00251 |
| Sonnet 5 | $0.00008 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
voyager-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 12d 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
Changelog Fragment Generator
Generate a Keep a Changelog fragment for the current changes.
Instructions
Step 1: Get PR number
PR_NUMBER=$(gh pr view --json number -q .number 2>/dev/null || echo "")
If $ARGUMENTS contains a number, use that. If no PR number is available from either source, ask the user to provide one or create the PR first.
Step 2: Analyze changes
git diff --stat origin/main...HEAD
git log --oneline origin/main..HEAD
Map commit types to fragment types:
| Commit type | Fragment type |
|---|---|
| feat | added |
| fix | fixed |
| security, deps (CVE) | security |
| perf, deps (routine) | changed |
| refactor, docs, style, test, build, ci, chore | skip (recommend skip-changelog label) |
Step 3: Write fragment
File: changes/{PR_NUMBER}.{type}.md
Set FRAGMENT_TYPE to the mapped type before writing, for example
FRAGMENT_TYPE=added.
Rules:
- 1-2 sentences, user-facing language
- Imperative present tense ("Add X" not "Added X")
- No file paths, commit hashes, or implementation details
Good: "Add workspace selector to the dashboard sidebar" Good: "Fix authentication token refresh loop on expired sessions" Good: "Upgrade requests library to address CVE-2026-25645" Bad: "Updated auth.ts to fix bug" Bad: "Refactored the codebase"
Step 4: Verify
test -s "changes/${PR_NUMBER}.${FRAGMENT_TYPE}.md"
cat "changes/${PR_NUMBER}.${FRAGMENT_TYPE}.md"
# When available, run the repo's fragment verifier
bash scripts/checks/verify-commit-changelog.sh
If no user-facing changes, tell the user to add the skip-changelog label instead.
Do not read or rewrite unrelated fragments while verifying this PR.
What ships with it
6 files 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.
- 12d ago First seen · 68 lines · 42 tokens per session scan A a7f4d5529c2b
voyager-changelog is a skill published in the GitHub repository fxd0h/Axelera-Voyager-Local-Assistant (4 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 503 once invoked, about $0.0002 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.