Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/sma1lboy/rove/releasenpx skills add Sma1lboy/rove --skill releasegit 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.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 | $0.00155 | $0.03289 |
| Opus 5 | $0.00077 | $0.01644 |
| Sonnet 5 | $0.00031 | $0.00658 |
| Haiku 4.5 | $0.00015 | $0.00329 |
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 yesterday.
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 — 228 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 automatic (
.github/workflows/changesets.yml, since 2026-08-12): any push tomaincarrying pending changesets triggers the full chain in Actions — CI-green wait → version+commit → tag → publish. When the user asks to release, FIRST check whether that workflow already has it:gh run list --workflow=changesets.yml --limit 3. If a run is mid-flight or completed for the relevant push, jump to Step 4 (watch the publish pipeline / verify npm). Run thescripts/release.shflow below only when the automatic path is unavailable (Actions down) or the user explicitly asks for the local flow — and never while a changesets.yml run is mid-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.
- yesterday Changed · +1 lines 87c7cf589b42
- 4d ago First seen · 227 lines · 155 tokens per session scan A 9481e35e948a
release is a skill published in the GitHub repository Sma1lboy/rove (115 stars, last pushed yesterday), licensed MIT. It adds 155 tokens to every session and 3,289 once invoked, about $0.0008 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
ai-change-impact
Measure what a change to an AI coding setup actually saved, in dollars. Compares recorded before/after usage from the AI Insights MCP server — either two specific sessions by id, or everything in one period against another — and attributes the cost difference to the factor that moved it: fewer API calls, less context…
ai-usage-review
Review recorded AI coding-tool usage and recommend concrete optimizations. Reads real token, cost, session and harness-configuration data from the AI Insights MCP server, then reports ranked, evidence-backed fixes — trimming instruction files, raising the prompt-cache hit rate, right-sizing models, cutting MCP…
Bun Patterns
Use this skill when working in Bun-based projects (or Node projects running on Bun) and you want reliable runtime expectations, dependency management, and debugging workflows.
Node.js Debugger
Use this skill when debugging runtime failures in Node.js or Bun: stack traces, async errors, startup crashes, port conflicts, and memory leaks.
google-meet
Google Meet via gws: create spaces, fetch join links, list recordings.
people-crm
Turn LinkedIn connections (or any contact export) into a queryable personal CRM using the agent database.