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/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/retz8/pastiche/release-pastiche"><img src="https://agentmods.dev/badge/skills/retz8/pastiche/release-pastiche.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.00066 | $0.00364 |
| Opus 5.5 | $0.00026 | $0.00146 |
| Sonnet 5.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 1mo 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.
- 1mo 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 4mo ago), licensed MIT. It adds 66 tokens to every session and 364 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-08-31.
Other skills, from other repositories
release-retrospective
Review how a shipped release, migration or deprecation went against its plan: blast radius, comms, migration, timeline, support load, each gap classed. Triggers: release retro, post-mortem, how did the deprecation go. Planning a new deprecation: deprecation-process.
version-bump-advisor
Decide the semver bump (major, minor or patch) for a design system release from a diff or change list, with reasoning and a CHANGELOG entry. Triggers: what version bump, is this breaking, major or minor. Release notes and announcements: change-communication. Migration scripts: codemod-generator.
shipping-and-launch
Use before any production deployment or release, when preparing to launch a feature, when validating release readiness, when a rollback plan is needed before shipping, or when a pre-launch gate is required before approving a deploy.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
ops-release
OPS on-demand: This skill should be used when the user asks to "release the plugin", "publish ops…
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.