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/savant0x/savant-code/release-workflownpx skills add savant0x/savant-code --skill release-workflowgit clone --depth 1 https://github.com/savant0x/savant-codeWhat 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.00023 | $0.00461 |
| Opus 5 | $0.00012 | $0.00230 |
| Sonnet 5 | $0.00005 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
release-workflow 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 2d 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 Workflow Standards
Mandatory Release Cycle
Every time code is pushed:
- Update CHANGELOG.md — add entries for all changes since last push
- Review README.md — update test counts, version references, any stale data
- Commit docs —
git add CHANGELOG.md README.md && git commit -m "docs: ..." - Push —
git push - Create/update release — tag + release notes on GitHub (or equivalent)
Never push code without updating CHANGELOG + README first. Never skip the release.
CHANGELOG Format
Follow Keep a Changelog:
## [VERSION] — YYYY-MM-DD
### Added
- New features
### Fixed
- Bug fixes
### Changed
- Modifications to existing behavior
### Removed
- Deprecated features
Group entries by FID when applicable. Include file references in parentheses.
README Maintenance
On every release, verify:
- Version number matches Cargo.toml / package.json
- Test count matches
cargo testoutput - FID count matches
dev/fids/directory - All referenced features still exist
- No stale links or descriptions
AGENTS.md
Each project should have an AGENTS.md at the root with:
- Project-specific release workflow (may override this standard)
- Build & test commands
- Protocol version reference
- Any project-specific conventions
Version Bumping
- Patch (0.1.0 → 0.1.1): Bug fixes, small improvements
- Minor (0.1.0 → 0.2.0): New features, non-breaking changes
- Major (0.1.0 → 1.0.0): Breaking changes, architecture shifts
Update VERSION file first, then propagate to all config files.
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.
- 2d ago First seen · 70 lines · 23 tokens per session scan A a1f04bc9e454
release-workflow is a skill published in the GitHub repository savant0x/savant-code (11 stars, last pushed 11d ago), licensed Apache-2.0. It adds 23 tokens to every session and 461 once invoked, about $0.0001 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-30.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
release-notes
Draft concise release notes.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
store-update
在 CCX Desktop 发布后下载 Store MSIX 并生成发布公告。用户提到 Store 上架、MSIX、从 GitHub Release 下载 store.msix、发布后同步 Windows Store、从 release 填写商店更新内容时必须使用此技能。该技能会下载最新 GitHub Release 的 amd64/arm64 MSIX，校验 sha256，从 Release body 生成 Store listing releaseNotes 预览，并输出手动上传指引。.