Borrowing it
Nothing to install: this file belongs to barockok/slaude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/barockok/slaude/main/.claude/skills/release-prep/SKILL.mdgit clone --depth 1 https://github.com/barockok/slaudeWrote 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/barockok/slaude/release-prep)<a href="https://agentmods.dev/skills/barockok/slaude/release-prep"><img src="https://agentmods.dev/badge/skills/barockok/slaude/release-prep/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/barockok/slaude/release-prep"><img src="https://agentmods.dev/badge/skills/barockok/slaude/release-prep.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.00049 | $0.01977 |
| Opus 5.5 | $0.00020 | $0.00791 |
| Sonnet 5.5 | $0.00010 | $0.00395 |
| Haiku 4.5 | $0.00005 | $0.00198 |
Grade C, and why
release-prep scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
SLAUDE_VERSION=X.Y.Z-rc.1 curl -fsSL https://raw.githubusercontent.com/barockok/slaude/main/install.sh | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
SLAUDE_VERSION=X.Y.Z-rc.1 curl -fsSL https://raw.githubusercontent.com/barockok/slaude/main/install.sh | bash How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Prep
Overview
Slaude release workflow. Granular commits, hand-written release notes, automated verification. Follows docs/site/_content/releases/<tag>.md convention from CLAUDE.md.
Two paths:
- Direct — bump, tag
vX.Y.Z, push. For patches and low-risk minors. - Release candidate — tag
vX.Y.Z-rc.Nfirst, soak, then promote tovX.Y.Z. Use for anything touching the install path, the DB schema, or the agent loop.
Both run the same release.yml; the RC path just publishes as a GitHub pre-release (auto-detected from the - in the tag) so install.sh never picks it up as latest.
When to Use
- User asks to prep/cut/ship a release
- Version bump needed
- Release notes need writing
- Post-merge release verification needed
Quick Reference
| Step | Command / Action |
|---|---|
| Find last tag | git describe --tags --abbrev=0 |
| Diff commits | git log <tag>..HEAD --oneline |
| Check changed files | git diff --stat <tag>..HEAD |
| Type check | bun run typecheck |
| Run tests | bun test |
| Installer smoke | bash tests/installer/smoke.sh |
| Promote an RC | scripts/promote-rc.sh vX.Y.Z-rc.N [--dry-run] |
Release Workflow
1. Diff since last tag
git describe --tags --abbrev=0
git log <tag>..HEAD --oneline --no-decorate
git diff --stat <tag>..HEAD
2. Determine version (semver)
- Major (
X.0.0): breaking schema/config/API change - Minor (
x.Y.0): new features, non-breaking additions - Patch (
x.y.Z): bugfixes only, no new features
Default to minor if any feat: commits since last tag. Patch only if all commits are fix:, docs:, test:, chore:.
3. Bump version
Edit package.json "version" field. Commit separately:
chore(release): bump version to X.Y.Z
4. Write release notes
Create docs/site/_content/releases/vX.Y.Z.md. Structure:
## vX.Y.Z — <one-line summary>
<paragraph describing release theme/motivation>
### Features
- **Area: feature name.** Description. Link to files if non-obvious.
### Fixes
- **Area: fix description.** What was broken, what changed.
### Internal
- Tests, docs, refactorings that don't affect runtime behavior.
### Commits
- `type(scope): subject` (short-sha)
- ...
**Full diff:** https://github.com/barockok/slaude/compare/vPREV...vX.Y.Z
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 Changed · +33 lines 8c94caf79bf0
- 2mo ago First seen · 179 lines · 49 tokens per session scan C 48c48fceffc2
release-prep is a skill published in the GitHub repository barockok/slaude (6 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 1,977 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). 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-announcement
A release-promotion tool that turns a project's latest Markdown release notes into a short WeChat group message and a vertical PNG poster. It checks GitHub contributor IDs and downloads their real public profile pictures; it does not create or publish a GitHub Release.
public-plugin-packaging
Use when packaging an Agentlas agent repo for public GitHub release, Codex plugin submission, Claude adapter distribution, or one-line terminal installation.
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
release-revoke
Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally revert the release commit. Use when the user says "revoke release", "rollback release", "delete release", "unpublish…
gh-monitor-pr
Start a detached GitHub pull-request monitor that wakes the exact launching Codex Desktop or CLI root through the managed Codex App Server when review, CI, conflict, merge-queue, closure, readiness, or merge events need attention. Use when the user asks Codex to watch, monitor, babysit, or wait on a PR or merge queue…
kirocrew-prepare-pr
LOAD THIS FOR EVERY KIRO CREW PR you open or update (Kiro Crew repo only; not other repos or CRs). Runs the whole loop — issue + tier, commit, sync, squash, push, drive CI and AI review to green, fix a red main, arm auto-merge and watch it land (24h). 'push my changes' = prepare-only.