Borrowing it
Nothing to install: this file belongs to PowerBeef/Vocello. 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/PowerBeef/Vocello/main/.claude/skills/vocello-release-readiness/SKILL.mdgit clone --depth 1 https://github.com/PowerBeef/VocelloWrote 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/powerbeef/vocello/vocello-release-readiness)<a href="https://agentmods.dev/skills/powerbeef/vocello/vocello-release-readiness"><img src="https://agentmods.dev/badge/skills/powerbeef/vocello/vocello-release-readiness/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/powerbeef/vocello/vocello-release-readiness"><img src="https://agentmods.dev/badge/skills/powerbeef/vocello/vocello-release-readiness.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.00034 | $0.00425 |
| Opus 5.5 | $0.00014 | $0.00170 |
| Sonnet 5.5 | $0.00007 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
vocello-release-readiness 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.
What it actually says
Release readiness (read-only)
Arguments: $ARGUMENTS
Read docs/reference/quality-promotion.md, docs/reference/macos-release-qa.md, docs/reference/ios-appstore-submission.md and
tooling-and-evidence.md. Require/infer the exact tag or candidate; inspect existing Git metadata,
GitHub checks and release assets through read-only tools. Candidate production and public promotion
are separate decisions; this skill authorizes neither. No release.sh, workflow dispatch, signing,
upload, metadata change, push, deployment or App Store write.
Validate existing source-authority inputs with python3 scripts/release_source_authority.py and
quality evidence with python3 scripts/quality_promotion.py validate; consult --help for required
arguments. Curated notes use python3 scripts/check_release_notes.py <tag>. Read-only GitHub GETs
may save fetched JSON to governed scratch, never into frozen evidence. The source-authority script has
no network route: save the tag ref (gh api --method GET repos/<owner>/<repo>/git/ref/tags/<tag>), the
annotated tag object, the tagged commit's check runs (.../commits/<sha>/check-runs?filter=all) and its
push runs on main (.../actions/runs?head_sha=<sha>&event=push&branch=main) under
build/scratch/transient/release-evidence/<tag>/, then pass those files to the script. Check annotated verified
tag, origin/main containment, exact tagged-SHA push CI, platform/lane completeness, evidence age
and compatible source/build/device identities. Missing evidence is a blocker, never an inferred PASS.
Report each check and what would unblock it. Publication requires a specific maintainer request.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 065bf3b843a0
- 18d ago First seen · 20 lines · 34 tokens per session scan A 11affda117f8
vocello-release-readiness is a skill published in the GitHub repository PowerBeef/Vocello (386 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 425 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-10-11.
Other skills, from other repositories
update-v8-version
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.
benchmark
Run performance + quality benchmarks. ASR reports WER, RTF, process memory, and throughput across engines/variants. Arguments include asr, tts, vad, diarize, asr-quick.
review-pr
Review a pull request for conceptual fit, architecture impact, adversarial failure modes, security risk, docs impact, regression risk, test coverage, and merge readiness. Use when asked to review a PR, check whether a PR is safe to merge, decide if more tests are needed, perform adversarial or security review, or…
release
Prepare, verify, and publish Sutando engine releases. Use when asked to prepare a release proposal, determine a version bump, audit release documentation, validate release gates, create a release PR, tag a confirmed release, or publish GitHub release notes. Preparation is safe and non-publishing; tagging and…
starcat-update-changelog
Update Starcat changelog documents in supports/starcat-pro/ by reading ALL git commits from the main Starcat project and generating categorized release notes in both English and Chinese. Use this skill whenever the user wants to update changelog, release notes, update records, or sync the changelog with recent…
publish-plugins
(project) Use when editing any file under skills/ or plugins/ to bump the plugin version and check the manifests.