Borrowing it
Nothing to install: this file belongs to backblaze-labs/genblaze. 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/backblaze-labs/genblaze/main/.claude/skills/release-check/SKILL.mdgit clone --depth 1 https://github.com/backblaze-labs/genblazeWrote 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/backblaze-labs/genblaze/release-check)<a href="https://agentmods.dev/skills/backblaze-labs/genblaze/release-check"><img src="https://agentmods.dev/badge/skills/backblaze-labs/genblaze/release-check.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.1 | $0.00055 | $0.00857 |
| Opus 5 | $0.00028 | $0.00428 |
| Sonnet 5 | $0.00011 | $0.00171 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
release-check 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 6d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release check — $ARGUMENTS
The release workflow is triggered by a published GitHub Release (see .github/workflows/release.yml).
publish-core runs first, then publish-cli and publish-connectors in parallel. Every package
needs its own version bump + CHANGELOG entry + passing tests before you tag.
Parse $ARGUMENTS as <package> <new-version> (e.g. core 0.3.2, openai 0.2.0).
Locate the package
| Package | Path |
|---|---|
core |
libs/core |
cli |
cli |
| any connector | libs/connectors/<name> |
Checklist
Run each step. Stop and report on the first failure.
- Version bump. Read
<path>/pyproject.toml. Ifversion!=$2, edit it to$2. - Core dependency pin (connectors only). Confirm
genblaze-core>=<x>is at or above the currently published core version. Ifcoreis also being released in this wave, the connector pin should match. - Entry point sanity (connectors only). Confirm the
[project.entry-points."genblaze.providers"]line exists and the module/class is importable:python -c "import genblaze_<name>; <name>.<Class>()" || true(instantiation may require credentials — just check the import). - Tests.
cd <path> && pytest -vmust pass. - Lint.
ruff check <path>andruff format --check <path>must pass. - Typecheck (core only; connectors optional).
mypy <path>/genblaze_*/ --ignore-missing-imports. - Build check.
cd <path> && python -m build && twine check dist/*— validates wheel metadata before PyPI sees it. - CHANGELOG. Confirm
CHANGELOG.mdhas an entry for version$2scoped to this package. If missing, draft one fromgit log --oneline $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~30)..HEAD -- <path>. - Doc freshness. For connectors: confirm the matching section in README.md and any
docs/features/provider-system.mdentry is accurate for$2.
Report
A pass/fail table, then the exact next commands:
git add <path>/pyproject.toml CHANGELOG.md
git commit -m "release: <package> v<new-version>"
git push
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.
- 6d ago First seen · 64 lines · 55 tokens per session scan A 9d90cdc49b44
release-check is a skill published in the GitHub repository backblaze-labs/genblaze (558 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 857 once invoked, about $0.0003 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
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.
pinned-release-checklist
Minimal guidance-only Skill used by release-pinned compatibility examples.
Release Checklist
Check release readiness and record a release note. Use for release and rollback requests.
Release Readiness Reviewer
Reviews a release candidate and produces a go/no-go readiness decision.
maf-release-watcher
Detects new MAF releases, extracts breaking changes, and keeps the toolkit's registry/matrix/guide current. Pipeline: (1) deterministic data extraction via GitHub Actions + Python helpers + dotnet-inspect, opens a PR with raw data and TODOs on a per-version branch (never commits direct to main), (2) optionally, a…
plainx-release
Releases plainx packages with version suggestions, changelog generation, and git tagging. Use when releasing a package to PyPI.