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 grimoire-rs/grimoire --skill changeloggit clone --depth 1 https://github.com/grimoire-rs/grimoireWrote 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/grimoire-rs/grimoire/changelog)<a href="https://agentmods.dev/skills/grimoire-rs/grimoire/changelog"><img src="https://agentmods.dev/badge/skills/grimoire-rs/grimoire/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/grimoire-rs/grimoire/changelog"><img src="https://agentmods.dev/badge/skills/grimoire-rs/grimoire/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.00086 | $0.01244 |
| Opus 5.5 | $0.00034 | $0.00498 |
| Sonnet 5.5 | $0.00017 | $0.00249 |
| Haiku 4.5 | $0.00009 | $0.00124 |
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 18d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/changelog — Site Changelog for a Release
CHANGELOG.md is git-cliff's commit-level record. The site page
docs/src/content/docs/changelog.md (served at /changelog.html) is the
user-facing one: what a user can do now that they could not before, why it
matters, and which doc page shows how. This skill adds one release to it.
Runs in the release ceremony between task release:prepare and the
release: vX.Y.Z commit (workflow-release.md).
An AI performing a release runs it too — the release is incomplete without it.
Before writing, load the docs skill, .claude/rules/docs-style.md and
.claude/rules/product-context.md for voice and link conventions.
Page contract
Newest first. page_type.py requires every ### inside a version section
to start with a version number, so feature headings are ####.
## 0.15 — <theme of the minor, user words> {#v0-15}
<2–3 sentences: who benefits and what changed for them, linking the
headline `####` sections across its releases.>
### 0.15.1 — 2026-10-12 {#v0-15-1}
<Highlights: 1–2 sentences naming this release's changes, each linked to
its `####` below.>
#### <Feature as the user's gain> {#v0-15-1-<slug>}
<Problem the user had → what they can do now → one short command or
config example → link to the guide or reference.>
#### Smaller improvements {#v0-15-1-more}
- <outcome bullet> — [doc page][ref].
- Every version (
###) opens with a highlights sentence or two that links each####in it. No release body starts with a heading or a list. - One
####per notable change: a feature, a new client, a TUI change, a breaking change (heading says so, body gives the migration). Never let a bullet list follow a feature's body directly — it reads as that feature's sub-items. Loose items go under a closing#### Smaller improvements(and#### Fixeswhen fixes are worth listing on their own). - Minor (x.y.0) — new
##section above the previous minor, plus### x.y.0. - Patch (x.y.z) — new
###directly under the minor's theme paragraph (patches newest first, abovex.y.0). A patch with nothing notable is highlights plus#### Smaller improvementsonly. Revisit the minor's theme paragraph when the patch shifts it. - Heading anchors:
{#vX-Y},{#vX-Y-Z},{#vX-Y-Z-<slug>}— never change an anchor once published. - Date = the version heading date in
CHANGELOG.md.
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.
- 18d ago First seen · 100 lines · 86 tokens per session scan A bf5e3191bfd0
changelog is a skill published in the GitHub repository grimoire-rs/grimoire (14 stars, last pushed today), licensed Apache-2.0. It adds 86 tokens to every session and 1,244 once invoked, about $0.0003 per session on Opus 5.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-29.
Other skills, from other repositories
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.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
submit-hook
Submit a deployed Uniswap v4 hook to the public univ4-hooks registry - format the listing, open a PR (issue fallback) so it lists on the hook marketplace.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
release
Versioning and CHANGELOG: SemVer mapped from Conventional Commits, Keep a Changelog format, tagging, pre-release gates. Use when cutting a version: bumping, writing the CHANGELOG entry, or tagging.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.