Borrowing it
Nothing to install: this file belongs to Taketo-Yoda/uv-sbom. 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/Taketo-Yoda/uv-sbom/develop/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/Taketo-Yoda/uv-sbomWrote 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/taketo-yoda/uv-sbom/release)<a href="https://agentmods.dev/skills/taketo-yoda/uv-sbom/release"><img src="https://agentmods.dev/badge/skills/taketo-yoda/uv-sbom/release/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/taketo-yoda/uv-sbom/release"><img src="https://agentmods.dev/badge/skills/taketo-yoda/uv-sbom/release.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.00013 | $0.04005 |
| Opus 5.5 | $0.00005 | $0.01602 |
| Sonnet 5.5 | $0.00003 | $0.00801 |
| Haiku 4.5 | $0.00001 | $0.00400 |
Grade A, and why
release 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 16d 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.
How it starts
The opening of the file, as written. The whole thing — 467 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release - Release Preparation Skill
Automates the pre-release preparation workflow, ensuring consistent version updates across all files and proper CHANGELOG management.
Language Requirement
IMPORTANT: All outputs (commits, PRs, branch names) MUST be written in English.
Scope Boundaries
What this skill DOES:
- Update version numbers in all required files
- Update CHANGELOG.md format
- Run pre-flight checks (fmt, clippy, test)
- Create release branch and PR to
develop
Merge Flow
release/vX.Y.Z → develop → main
- Step 8 creates a PR:
release/vX.Y.Z→develop - After merge, the user opens a second PR:
develop→main(with tag creation)
What this skill does NOT do (manual steps):
- Tag creation - User must manually create and push the tag after PR merge
- PR merge - User must manually review and merge the PR
- Post-release verification - User must verify the release was successful
This separation ensures human oversight for the irreversible release action (tag push triggers CI/CD).
Pre-flight Checks (MANDATORY)
Before proceeding with version updates, ALL of the following checks MUST pass. The
commands below are a derived copy of .claude/conventions/ci-checks.md; this skill
intentionally uses the write-mode cargo fmt --all (format, then verify) instead of
--check.
1. Format Code
cargo fmt --all
2. Clippy Check
cargo clippy --all-targets --all-features -- -D warnings
CRITICAL: Zero warnings required. Fix all issues before proceeding.
3. Test Suite
cargo test --all
All tests must pass.
Steps
Step 0: Validate Current Branch (MANDATORY)
git branch --show-current
CRITICAL: Must be on develop or a feature branch. Cannot release from main.
| Current Branch | Action |
|---|---|
main |
❌ STOP - Cannot release from main |
develop |
✅ Proceed |
feature/* |
✅ Proceed |
bugfix/* |
✅ Proceed |
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.
- 16d ago Changed · +7 lines 9513867754eb
- 18d ago Changed · +59 lines 6e2312386fd3
- 25d ago Changed · +7 lines 31944c2100d9
- 1mo ago First seen · 394 lines · 13 tokens per session scan A 0ca969346313
release is a skill published in the GitHub repository Taketo-Yoda/uv-sbom (6 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 4,005 once invoked, about $0.0001 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-09-04.
Other skills, from other repositories
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
mem0-integrate
Integrate Mem0 into an existing repository using a goal-driven, TDD pipeline. Detects the repo's language automatically and asks the user to pick between Mem0 Platform (managed) and Mem0 Open Source (self-hosted). Writes failing tests before any implementation. Produces a local feature branch plus .mem0-integration/…
validate-release-green
Run or inspect the local Release-Green observer for an exact base or combined PR candidate, separating hard failures, advisory drift and incomplete evidence. Use for maintainer preflight; full CI acceptance remains a separate requirement.
xberg-release
Xberg release on top of the shared release-workflow: mise run version:sync to bindings and chart, CI/Publish/Benchmarks readiness. Use before a release.
ship
Pre-release gate. Run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.