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 agentmods add skills/barockok/slaude/release-prepnpx skills add barockok/slaude --skill release-prepgit 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.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 | $0.00049 | $0.01534 |
| Opus 5 | $0.00024 | $0.00767 |
| Sonnet 5 | $0.00010 | $0.00307 |
| Haiku 4.5 | $0.00005 | $0.00153 |
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 4d 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 — 179 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/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/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.
- 4d ago First seen · 179 lines · 49 tokens per session scan C 48c48fceffc2
release-prep is a skill published in the GitHub repository barockok/slaude (5 stars, last pushed 5d ago), licensed MIT. It adds 49 tokens to every session and 1,534 once invoked, about $0.0002 per session on Opus 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
Prepare and publish stable Agent Lightning releases through the repository's version bump, pull-request checks, merge, tag, PyPI trusted-publishing, and versioned-documentation workflows. Use when asked to plan, cut, verify, or explain a release; treat nightly TestPyPI builds as a separate path.
herdr-pre-release-audit
Audit herdr release readiness by comparing commits since the base release against next-release changelog and docs. Use when asked to run or apply the repo's pre-release audit, validate docs/next before release, inspect issue refs that release CI will close, or finalize release docs for herdr.
release-notes
Generate user-facing release notes for Intelligent Terminal. Use when asked to write release notes, changelog, what-is-new summary, or prepare a release. Compares git commits between releases, looks up PR-linked issues and community contributors, then outputs formatted notes with "Verbed + Impact + Scenario" style…
github-ops
GitHub CLI for issues, PRs, code search, CI logs, releases, and API queries. Requires gh CLI and auth.
parallel-pr-review
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.
Release Notes Generator
Generate professional software release notes from a commit log: classify changes, write user-facing summaries, draft a publishable announcement, and assess release readiness. Use for release, changelog, version, and deploy requests.