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-governed-release-methodologygit 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-governed-release-methodology)<a href="https://agentmods.dev/skills/cratis/ai/cratis-governed-release-methodology"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-governed-release-methodology/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-governed-release-methodology"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-governed-release-methodology.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.00087 | $0.03520 |
| Opus 5 | $0.00044 | $0.01760 |
| Sonnet 5 | $0.00017 | $0.00704 |
| Haiku 4.5 | $0.00009 | $0.00352 |
Grade A, and why
cratis-governed-release-methodology 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 2d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Governed release methodology
Release engineering is the discipline of matching ceremony to consequence. Too little, and a consumer upgrades into a broken build with no way back. Too much, and every documentation fix drags a supply-chain ritual behind it until the ritual is performed without belief and stops meaning anything.
This skill is product-, language-, and registry-independent. It applies to a
Cratis repository publishing NuGet packages, one publishing npm packages, one
pushing container images, and one whose whole delivery is a merge to main. It
grants no release authority of its own: it tells you what a claim costs, not
that you may make it.
Start with the artifact, not the process
The single most expensive mistake is applying package-release ceremony to something that is not a package. Classify the artifact first.
| Artifact | What the consumer receives | Ceremony it earns |
|---|---|---|
| Compiled package (NuGet, npm, Maven, Hex), container image, installer | Opaque bytes built on infrastructure the consumer cannot inspect | Full supply-chain receipts |
| Generated or bundled tree assembled by a pipeline | Bytes that do not exist in any reviewed source tree | Full supply-chain receipts |
| Source files a host reads directly from a git ref (rules, skills, templates) | Exactly the reviewed content at a commit | Review and versioning only |
The dividing question is "can the consumer verify what they got against what was reviewed, without trusting our build?" If the host clones a git ref and reads the files, git's own content addressing already answers that: the tree hash is the checksum, the commit is the provenance, and the reviewed diff is the artifact. Generating a checksum file for that content, publishing an SBOM of markdown, and demanding a signed attestation before a folder may be read adds process without adding a guarantee. Say so plainly rather than performing it.
If the artifact is compiled or assembled, the opposite holds, and the supply-chain receipts below are not optional decoration.
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.
- 2d ago First seen · 298 lines · 87 tokens per session scan A dd3f76ca2752
cratis-governed-release-methodology is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 3,520 once invoked, about $0.0004 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-06.
Other skills, from other repositories
update-changelog
Update the CHANGELOG.md files of C# projects. Parameters: csroot C# SDK repository root.
create-release
Create a versioned GitHub release with changelog.
safe-github-push
A workflow for safely pushing Git repositories that contain large assets or binary files to GitHub. It checks repository changes and file sizes before planning commits and pushes.
bump-version
Bump the SSW.VerticalSliceArchitecture.Template NuGet package version to cut a new release. Use when the user says "bump the version", "cut a release", "release a new version", "publish a new package version", or similar for this template repo. Edits the version in VerticalSliceArchitecture.nuspec — which is what…
release
Prepare and publish Perigon.CLI patch releases, including versioning, release notes, bilingual docs, validation, and the nuget-branch CI handoff.
create-release
Skill "create-release" from markmhendrickson/neotoma, covering create new release, when to use, prerequisites, command execution and step 1: load documentation.