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 Cratis/AI --skill cratis-release-notesgit clone --depth 1 https://github.com/Cratis/AIWrote 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/cratis/ai/cratis-release-notes)<a href="https://agentmods.dev/skills/cratis/ai/cratis-release-notes"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-release-notes/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/cratis/ai/cratis-release-notes"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-release-notes.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.00054 | $0.01913 |
| Opus 5.5 | $0.00022 | $0.00765 |
| Sonnet 5.5 | $0.00011 | $0.00383 |
| Haiku 4.5 | $0.00005 | $0.00191 |
Grade A, and why
cratis-release-notes 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 7d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release notes for the person upgrading
An upgrader wants to know whether their application changes, what will break,
and what to do before installing. A feature list and a list of pull request
titles cannot answer that. This skill writes the communication, not the
release decision. The repository's release workflow owns version intent,
gates, publication and recovery; drafting never authorizes publishing or
editing a release. If the task also includes release planning, select the
separate cratis/methodology/governed-releases profile as needed; that is not
required to draft notes.
Establish the exact subject
Before writing, identify product, tag or candidate version, previous version, artifact/package names, supported platforms, and the audience. Inventory observable changes from the diff, specs, linked issues/PRs, and authoritative product source at that revision. A PR description is published verbatim as release notes in a Cratis repository; follow its current template and the pull-request contract, and confirm that behavior before drafting. Do not turn a draft into a claim about shipped behavior.
For each change, ask: who uses this path, what happened before, what happens now, is action required, and how would they notice? Check changed defaults, serialization/schema/data migrations, runtime and dependency compatibility, deploy ordering, deprecations/removals, and upgrade/rollback limits. Report what was not verified to the requester or in a PR comment; the published note states only verified facts and never says 'not verified'.
Cratis products move together at their seams: the Chronicle kernel and its clients, Arc and Chronicle, Components and Arc. When a change touches a seam, state supported pairings as facts the reader can act on ('Requires Chronicle kernel 19.25 or later'). Which pairings were tested, and against which branch or commit, is evidence for the PR comment. There is no central compatibility matrix to defer to, so the release note may be the only place a reader learns the supported pairings. Where a measurement drove the change, such as how many deployments hit a failure, give the number; never estimate one to add weight.
What ships with it
2 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.
- 7d ago Changed 1c771d6a958f
- 9d ago Changed · +2 lines cb687d29ac3b
- 12d ago Changed · +1 lines 585d76e12ccb
- 20d ago Changed · +3 lines 86d21571657a
- 21d ago Changed · +31 lines bf2efd016508
- 27d ago Changed · +16 lines 40848854beca
- 29d ago First seen · 88 lines · 54 tokens per session scan A 8b6dd7d16314
cratis-release-notes is a skill published in the GitHub repository Cratis/AI (4 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 1,913 once invoked, about $0.0002 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-23.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…