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 retz8/pastiche --skill release-pastichegit clone --depth 1 https://github.com/retz8/pasticheWrote 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/retz8/pastiche/release-pastiche)<a href="https://agentmods.dev/skills/retz8/pastiche/release-pastiche"><img src="https://agentmods.dev/badge/skills/retz8/pastiche/release-pastiche.svg" alt="Measured on agentmods" 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.00066 | $0.00364 |
| Opus 5 | $0.00033 | $0.00182 |
| Sonnet 5 | $0.00013 | $0.00073 |
| Haiku 4.5 | $0.00007 | $0.00036 |
Grade A, and why
release-pastiche 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.
What it actually says
release-pastiche
Run on main, clean working tree, after every task of the group has merged.
Workflow
- Determine the version. Default: the completed group's minor from
_dev/TODO.md(provisional — confirm with the user; hotfix releases are a patch bump instead). - Bump
versioninpackage.json. - Build:
npm run build— verifydist/claude-code/regenerated and itsplugin.jsoncarries the new version. - CHANGELOG entry. Move
[Unreleased]content (if any) and derive the rest from commits since the last release tag:feat(...)→ Added,fix(...)→ Fixed, breaking/behavior changes → Changed. Section header:## [<version>] - <today>. Fresh empty[Unreleased]on top. - Commit everything as one commit:
chore(release): v<version>. - Tag
v<version>and push branch + tag. - GitHub Release:
gh release create v<version>with the new CHANGELOG section as body. - Close the milestone for the shipped group.
- Tick TODO.md: confirm all the group's task checkboxes are ticked and parent issues closed; flag any that aren't.
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 First seen · 21 lines · 66 tokens per session scan A cc60f3cba9f6
release-pastiche is a skill published in the GitHub repository retz8/pastiche (4 stars, last pushed 3mo ago), licensed MIT. It adds 66 tokens to every session and 364 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
release-retrospective
Produce a structured look-back after a major release or deprecation — capturing what the plan got right, what it missed, and what to do differently. Trigger when someone says: release retrospective, post-release review, what went wrong with the release, how did the deprecation go, release post-mortem, retro on the…
version-bump-advisor
Recommend the correct semver bump with reasoning and a generated changelog entry. Trigger when someone says: what version bump, is this a breaking change, semver recommendation, should this be major or minor, version this release, changelog entry, what kind of release is this, or anything about versioning a design…
ship
Ship a build — pre-flight checks, deploy, document, verify, monitor. Use when deploying code, publishing packages, or releasing.
release
Prepare a version release — bump version files, commit, and tag. Just run /release with no arguments.
release-init
Detect project type and generate a tailored project-level /release skill. Run once per project to set up releasing.
release-plugin
Cut a cairn plugin release for a given MAJOR.MINOR.PATCH version, running every pre-flight and version gate before anything is changed or published.