Borrowing it
Nothing to install: this file belongs to r3bl-org/r3bl-open-core. 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/r3bl-org/r3bl-open-core/main/.agents/skills/release-crate/SKILL.mdgit clone --depth 1 https://github.com/r3bl-org/r3bl-open-coreWrote 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/r3bl-org/r3bl-open-core/release-crate)<a href="https://agentmods.dev/skills/r3bl-org/r3bl-open-core/release-crate"><img src="https://agentmods.dev/badge/skills/r3bl-org/r3bl-open-core/release-crate/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/r3bl-org/r3bl-open-core/release-crate"><img src="https://agentmods.dev/badge/skills/r3bl-org/r3bl-open-core/release-crate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 115 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00034 | $0.01355 |
| Opus 5 | $0.00017 | $0.00678 |
| Sonnet 5 | $0.00007 | $0.00271 |
| Haiku 4.5 | $0.00003 | $0.00136 |
Grade A, and why
release-crate 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 10d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crate Release
When to Use
- When the user says "release", "publish", or invokes
/release <crate> - The argument is the crate directory name:
build-infra,tui,cmdr,analytics_schema- The crate name begins with
r3bl-prefix for binary crates andr3bl_prefix for library crates - the prefix is applied to the folder name of the crate (e.g.,r3bl_tuicrate is intuifolder, andr3bl-cmdrcrate is in thecmdrfolder). - Always look at the Cargo.toml file of the crate to verify the crate name and version before invoking the release skill.
- The crate name begins with
Prerequisites
Before starting a release, verify:
- All code changes are complete and tested
./check.fish --fullpasses (or equivalent checks have been run recently)- You know the new version number (ask the user if not specified)
Release Workflow
Follow these steps in order. Reference docs/release-guide.md for canonical examples.
Step 1. Determine crate and version
- Identify the crate directory from the argument
- Read
<crate>/Cargo.tomlto find the current version - Determine the new version (ask the user if not specified)
- Identify if this is a binary crate (
build-infra,cmdr) or library crate (tui,analytics_schema)
Step 2. Bump version in <crate>/Cargo.toml
- Update the
versionfield to the new version
Step 3. Update CHANGELOG.md
- Add the new version entry under the crate's section (before existing entries)
- Follow the existing format:
### vX.Y.Z (YYYY-MM-DD)with summary, Fixed/Added/Changed sections - Update the TOC at the top of the file to include the new entry
Step 4. Update docs/release-guide.md
- Update the version number in the script block for the crate being released
- Update the git commit and tag lines to reflect the new version
Step 5. Run build, test, docs, clippy, fmt
./check.fish --full
Or if check.fish is unavailable, run manually:
cd <crate>
cargo build && cargo test && cargo doc --no-deps && cargo clippy --fix --allow-dirty --allow-staged && cargo fmt --all
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.
- 10d ago First seen · 183 lines · 34 tokens per session scan A 0ad992d852dd
release-crate is a skill published in the GitHub repository r3bl-org/r3bl-open-core (483 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 1,355 once invoked, about $0.0002 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
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
cw-orient
Use at the start of any Codewhale work session, or when unsure which checkout, branch, or worktree is authoritative: establish live repo truth before reading a plan or editing a file.
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-close-issues
Close resolved Codewhale issues only after verifying the landed commit/behavior, with a positive crediting comment; never from title alone.