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/recent-releasenpx skills add Sma1lboy/rove --skill recent-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/recent-release)<a href="https://agentmods.dev/skills/sma1lboy/rove/recent-release"><img src="https://agentmods.dev/badge/skills/sma1lboy/rove/recent-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.1 | $0.00112 | $0.01291 |
| Opus 5 | $0.00056 | $0.00646 |
| Sonnet 5 | $0.00022 | $0.00258 |
| Haiku 4.5 | $0.00011 | $0.00129 |
Grade A, and why
recent-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 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recent Release Page (Rove)
Turns recent Rove releases into a single self-contained HTML file styled like the product itself — the claude theme palette, JetBrains Mono, a terminal title bar, FEAT/FIX tags. It is the shareable, human-facing companion to changelog-generator (which writes the machine-consumed Changesets). This skill only renders; it never edits CHANGELOG.md or changesets.
Default output language is Chinese (zh-CN) — Rove's default. Switch to English only if the user asks.
When to use
- "做一份发版速览 / release page / 把最近几个版本做成网页 / recent release html".
- The user wants to share or post what shipped (a page they can open in a browser or attach).
- After cutting one or more releases, to produce a readable summary page.
Do NOT use this to draft changelog entries — that's changelog-generator. This skill consumes already-shipped notes.
Inputs
- Version range. Default: the releases from today plus any from the last ~2–3 days so "几个发版" has content (Rove ships multiple releases/day — see the
main moves fastreality). If the user names a range ("0.7.34 → 0.7.37", "最近 5 个版本", "今天的"), honor it exactly. - Language. Default zh-CN.
enon request. - Output path. Default
rove-release-notes-zh.htmlat the repo root (-ensuffix for English). Honor an explicit path.
How to build
- Gather the releases. Read the top of
packages/kobe/CHANGELOG.mdfor the version sections in range. Cross-check dates withgit log --pretty="%h %ad %s" --date=short | grep -i "chore: release"so each version gets its real release date and "today" is correct (the env'scurrentDateis the reference for "today"). - Filter to user-facing. Keep features, visible behaviour changes, bug fixes the user can feel, packaging/install changes. Drop entries the changeset marked internal — anything starting
Internal:/Internal (web):/ pure refactor / test-only / "No behavior change". Same bar aschangelog-generator's Filtering section: "would a user reading github.com/Sma1lboy/rove/releases care?" - Classify each kept entry as
FEAT(new capability) orFIX(bug/behaviour fix). Map from the verb: "Add/新增" → FEAT, "Fix/修复" → FIX. Internal-but-shipped tooling (e.g.rove export) is FEAT. - Translate to natural Chinese (unless
en). Keep code identifiers, CLI commands, key chords, file paths, and the version numbers verbatim — only prose is translated. Render key chords with the.kbdstyle, code with<code>. - Fill the template. Copy
assets/template.htmland replace the marked regions;assets/example.htmlis a complete worked output (0.7.34 → 0.7.37) — match its density and voice. The newest version gets thetodaybadge (<span class="ver-badge today">今天</span>); older versions get a plain date. Keep the styling block byte-for-byte — it encodes the realclaudetheme values; do not invent colors. - Write the file to the output path and tell the user how to open it (suggest
! open <path>so it runs in their session). Do not auto-commit unless asked.
What ships with it
2 files 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.
- 6d ago First seen · 55 lines · 112 tokens per session scan A f56f1a76caed
recent-release is a skill published in the GitHub repository Sma1lboy/rove (116 stars, last pushed today), licensed MIT. It adds 112 tokens to every session and 1,291 once invoked, about $0.0006 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
deploy-safely
Build, test, push, deploy, and verify with rollback through Git on failure.
fable-release
Audit and certify repository merge and release readiness against required quality gates, clean git working trees, and verified distribution artifacts. Use when preparing a release tag, validating release checklist criteria, publishing npm/PyPI packages, or certifying a branch for merge — even if the user does not…
pr-explainer
Use when writing pull request descriptions, release notes, or summary diffs.
git-expert
Use this skill for version control best practices. Covers branching, commit messages, PR conventions, worktree management, and conventional commit automation.
git-workflow
Use this skill for version control best practices. It defines branching, commit messages, and PR conventions.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.