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-engineering-release-trainsgit 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-engineering-release-trains)<a href="https://agentmods.dev/skills/cratis/ai/cratis-engineering-release-trains"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-engineering-release-trains/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-engineering-release-trains"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-engineering-release-trains.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.00106 | $0.02258 |
| Opus 5.5 | $0.00042 | $0.00903 |
| Sonnet 5.5 | $0.00021 | $0.00452 |
| Haiku 4.5 | $0.00011 | $0.00226 |
Grade A, and why
cratis-engineering-release-trains 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 yesterday.
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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
One assembled candidate, one release
A candidate is the branch assembling deliveries intended to ship together. A repository includes its main checkout and all its worktrees. Consider their concurrent work together, not as separate releases merely because it has separate branches. One person or session assembles the candidate.
Authority and routing
Read capability-is-not-authority.md and the ship-changes prompt before any external effect. A user's ship request authorizes its ordinary shipping steps; loading this skill does not turn an implementation-only request into shipping. Without that request, prepare the grouping and report the proposed next action.
Read pull-requests.md for release intent, split criteria, release notes, issue dispositions, and the human checkpoint for a major release. A major release is never merged by an agent: a human confirms and merges it. Agent work stops at preparing the PR, even after confirmation. Read git-commits.md before assembling branches. Preserve commits: never squash, rebase, amend, or force-push.
Use cratis-engineering-consolidation-guard when folding existing PRs to prove
nothing was dropped. Use cratis-engineering-ci-gates for gate selection and
run handling, and cratis-engineering-review-rounds for proportionate review.
Choose the candidate before creating a PR
-
Inspect the repository's worktrees, finished branches, and open PRs:
git worktree list gh pr list --state open --json number,headRefName,title,author -
Group related, ready deliveries under one candidate and one PR. Check with the person assembling an existing candidate before changing it. Independent work branches start from
origin/main; work that depends on an unmerged candidate may start from that candidate's latest commit (see Replace waits with local work). Ongoing work keeps its branch. Do not edit another session's checkout or include its uncommitted work. -
Prefer joining a related open PR that is still accepting deliveries, has no checks running, and is not being merged by another session. Agree on its writer, merge
origin/maininto its branch, then merge the deliveries and extend its release note. Do not open a competing PR while it is being cut. -
If no candidate exists, create a branch from current
origin/mainand merge ready delivery branches with merge commits. Keep each logical change in its own commits. Return a conflicting or failing delivery for correction rather than guessing its intent in the assembled branch. -
Keep one candidate per repository by default. Apply the split criteria in
pull-requests.mdfor unrelated work, different risk, or an urgent fix. Name the exception in the reviewer comment; a major awaiting human confirmation must not silently hold unrelated safe work indefinitely.
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.
- yesterday First seen · 192 lines · 106 tokens per session scan A cb7fad5fa373
cratis-engineering-release-trains is a skill published in the GitHub repository Cratis/AI (4 stars, last pushed today), licensed MIT. It adds 106 tokens to every session and 2,258 once invoked, about $0.0004 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-10-25.
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…