Borrowing it
Nothing to install: this file belongs to mihai-dinculescu/tapo. 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/mihai-dinculescu/tapo/main/.claude/skills/release-libs/SKILL.mdgit clone --depth 1 https://github.com/mihai-dinculescu/tapoWrote 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/mihai-dinculescu/tapo/release-libs)<a href="https://agentmods.dev/skills/mihai-dinculescu/tapo/release-libs"><img src="https://agentmods.dev/badge/skills/mihai-dinculescu/tapo/release-libs/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/mihai-dinculescu/tapo/release-libs"><img src="https://agentmods.dev/badge/skills/mihai-dinculescu/tapo/release-libs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.00703 |
| Opus 5 | $0.00015 | $0.00351 |
| Sonnet 5 | $0.00006 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
release-libs 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 9d 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.
Release tapo & tapo-py
Release a new version of the tapo (Rust) and tapo-py (Python) crates. Both libraries are released simultaneously and share the same version number.
Steps
-
Determine the new version. Read the current version from
tapo/Cargo.toml. Ask the user what the new version should be if not provided. -
Bump the versions. Update the
versionfield in both:tapo/Cargo.tomltapo-py/pyproject.toml
-
Update changelog. In
CHANGELOG.md:- Replace the heading
## [Python Unreleased][Unreleased]with## [Python vX.X.X][vX.X.X] - YYYY-MM-DD(use the current date). - Replace the heading
## [Rust Unreleased][Unreleased]with## [Rust vX.X.X][vX.X.X] - YYYY-MM-DD(use the current date). - Insert new empty
## [Rust Unreleased][Unreleased]and## [Python Unreleased][Unreleased]sections (in that order) immediately above the newly versioned Rust section. - If a
## [MCP Unreleased][Unreleased]section exists elsewhere in the file, move it (with its body intact) so it sits immediately after the new## [Python Unreleased][Unreleased]section, keeping all three Unreleased sections grouped at the top in the order Rust → Python → MCP. - Add a link reference
[vX.X.X]: https://github.com/mihai-dinculescu/tapo/tree/vX.X.Xto the link definitions at the bottom of the file (right after the[Unreleased]link).
- Replace the heading
-
Commit. Run
/commitwith messagechore(tapo): release vX.X.X. -
Tag. Create an annotated git tag:
git tag -a vX.X.X -m "vX.X.X" -
Push. Ask the user for confirmation, then:
git push && git push origin vX.X.X -
Create GitHub release. Ask the user for confirmation. Use the content under the
## [Rust vX.X.X][vX.X.X]and## [Python vX.X.X][vX.X.X]headings fromCHANGELOG.mdas the release body, followed by a full changelog comparison link. The previous version (vP.P.P) is the tag before this release:gh release create vX.X.X --title "Tapo vX.X.X" --notes "$(cat <<'EOF' ## Rust <rust changelog content here> ## Python <python changelog content here> **Full Changelog**: https://github.com/mihai-dinculescu/tapo/compare/vP.P.P...vX.X.X EOF )"
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.
- 9d ago First seen · 55 lines · 31 tokens per session scan A 652dd8bf858f
release-libs is a skill published in the GitHub repository mihai-dinculescu/tapo (800 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 703 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.