Borrowing it
Nothing to install: this file belongs to Sma1lboy/rove. 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/Sma1lboy/rove/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/Sma1lboy/roveWrote 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/sma1lboy/rove/release)<a href="https://agentmods.dev/skills/sma1lboy/rove/release"><img src="https://agentmods.dev/badge/skills/sma1lboy/rove/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/sma1lboy/rove/release"><img src="https://agentmods.dev/badge/skills/sma1lboy/rove/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, 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 33 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.
- high Tool Misuse · line 34 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.
- high Privilege Escalation · line 210 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00160 | $0.03203 |
| Opus 5.5 | $0.00064 | $0.01281 |
| Sonnet 5.5 | $0.00032 | $0.00641 |
| Haiku 4.5 | $0.00016 | $0.00320 |
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 17d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Rove
Autonomous release driver for @sma1lboy/rove. This is the supervised loop the
manual flow in docs/RELEASING.md describes — read
that doc once if anything here is ambiguous; it is the source of truth and this
skill must never contradict it.
Releases are on demand. Merging a PR only banks its changeset; nothing ships until someone runs
.github/workflows/changesets.yml(CI-green wait → version + commit → tag → dispatchrelease.yml). That workflow is the default path: do Step 1 againstorigin/main(the workflow releases whatever is banked there), thengh workflow run changesets.yml --ref main, find the run withgh run list --workflow=changesets.yml --limit 1, watch it withgh run watch <run-id> --exit-status, and go to Step 4. Use the localscripts/release.shflow (Steps 0–3) only when Actions is unavailable or the user asks for it, and never while a changesets.yml run is in flight on the same version (they'd race to tag it).
The job is: detect the bump → gate → bump/tag/push → watch CI → confirm published, or stop with a precise report. Do the whole chain without hand-holding, but stop and surface (never guess) at the two human-judgment gates marked ⚠ ASK below.
Hard rules (non-negotiable)
- Never force-push. No
git push -f, no--force-with-lease, nogit reset --hardon a shared branch, no retag-over-existing. If a tag or push conflicts, stop and report — recovery is the user's call. - Bump default is
patch. Per AGENTS.md: pre-1.0 Rove ships features as patches. Aminor/majoronly happens when the user explicitly said so this turn, OR a pending changeset already carries that bump — and the second case is exactly the trap to flag (see Step 1). - Release lands on
mainonly. Verify branch before and after. A release on a stray feature branch is the #1 historical failure — catch it early. - No
--no-verify, no skipping hooks. If a gate fails, fix the cause or stop. - The release commit is
chore: release — X.Y.Z. No AI/Claude attribution anywhere (commit, tag, GitHub release body).
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.
- 17d ago Changed · -5 lines a31d3bcb1b0d
- 28d ago Changed · +5 tokens per session 22a83e6690e3
- 1mo ago Changed · +1 lines 87c7cf589b42
- 1mo ago First seen · 227 lines · 155 tokens per session scan A 9481e35e948a
release is a skill published in the GitHub repository Sma1lboy/rove (178 stars, last pushed today), licensed MIT. It adds 160 tokens to every session and 3,203 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
gh-monitor-pr
Start a detached GitHub pull-request monitor that wakes the exact launching Codex Desktop or CLI root through the managed Codex App Server when review, CI, conflict, merge-queue, closure, readiness, or merge events need attention. Use when the user asks Codex to watch, monitor, babysit, or wait on a PR or merge queue…
dev-git-workflow
Designs team Git workflows for branching, PRs, and releases. Use when choosing branching models, stacked PRs, merge queues, worktree isolation for agents, or collaboration rules.
deploy-safely
Build, test, push, deploy, and verify with rollback through Git on failure.
changelog
Generate or update CHANGELOG.md with an entry for the unreleased changes since the last git tag. Invoke when the user asks to cut a release, update the changelog, or summarize changes since v-something.
manifest
Full autonomous SDLC — design, plan, implement, review, and ship with 4 human approval gates.
seal
Ships a feature — simplify pass, certify, commit, PR, CI monitoring, review loop, merge. Use when a feature branch is verified and ready to ship.