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 ractive/hyalo --skill hyalo-changeloggit clone --depth 1 https://github.com/ractive/hyaloWrote 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/ractive/hyalo/hyalo-changelog)<a href="https://agentmods.dev/skills/ractive/hyalo/hyalo-changelog"><img src="https://agentmods.dev/badge/skills/ractive/hyalo/hyalo-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/ractive/hyalo/hyalo-changelog"><img src="https://agentmods.dev/badge/skills/ractive/hyalo/hyalo-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.00024 | $0.00172 |
| Opus 5 | $0.00012 | $0.00086 |
| Sonnet 5 | $0.00005 | $0.00034 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
hyalo-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 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.
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 maintenance
Inspect hyalo config and hyalo changelog --help before editing.
The configured changelog may be outside the notes directory, relative to the project
configuration. Follow that path rather than assuming a vault-local CHANGELOG.md.
Use hyalo changelog add --help or hyalo changelog release --help for the exact
arguments. Preserve the existing Keep a Changelog sections and release history.
Moving entries into a release requires the requested version and release scope;
do not invent a release or publish artifacts while writing release notes.
Use hyalo lint --profile changelog --format text to inspect conformance.
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.
- 4d ago First seen · 19 lines · 24 tokens per session scan A 86a78b60e09a
hyalo-changelog is a skill published in the GitHub repository ractive/hyalo (24 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 172 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-09-07.
Other skills, from other repositories
releasing
Use before any release work: the trunk release model, the unstable edge channel, the prepare/release/promotion machinery, release-notes pages, the pre-release artifact smoke test, and, when the plugin channel is enabled, the Claude Code plugin channel.
publish-pr
Use in /implement at the draft→ready boundary to squash the branch's review-iteration commits into one (non-interactive soft-reset + recommit + force-with-lease) and mark the draft PR ready. Takes the commit message as input (sourced from the plan-file before cleanup). GitHub-specific (gh) behind a host-neutral…
synthetic-release-notes
Draft release notes from user-provided changes.
release-rollback
A release and rollback checklist for code or scripts, covering readiness checks, release decisions, and recovery after an incident.
changelog-writer
Use when a release is being prepared and a human-readable changelog must be generated from merged pull requests.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.