tapo: Skill for Claude Code

.claude/skills/release-libs/SKILL.md

release-libs is a skill for Claude Code from mihai-dinculescu/tapo. It costs 31 tokens per session (703 once invoked), scanned A, original, MIT.

A release procedure for publishing the Rust library tapo and its Python library tapo-py together under one version number. It updates both package files and organises the changelog for the release.

In plain words
What is it for?
Use it to choose a release version, update package metadata, prepare dated changelog sections, and coordinate the Rust and Python releases.
Why use it?
It prevents the two related libraries from receiving mismatched versions or incomplete release notes.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is mihai-dinculescu/tapo's own configuration. It tells Claude Code how to work on tapo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything tapo configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/mihai-dinculescu/tapo/main/.claude/skills/release-libs/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/mihai-dinculescu/tapo

Made for: Claude Code.

Wrote 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.

agentmods badge for release-libs

README.md
[![agentmods](https://agentmods.dev/badge/skills/mihai-dinculescu/tapo/release-libs/github.svg)](https://agentmods.dev/skills/mihai-dinculescu/tapo/release-libs)
Your own site
<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.

agentmods 80×15 button for release-libs

Your own site · 80×15
<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>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 703 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 9d ago against content hash 652dd8bf858f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

.claude/skills/release-libs/SKILL.md · 55 lines

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

  1. Determine the new version. Read the current version from tapo/Cargo.toml. Ask the user what the new version should be if not provided.

  2. Bump the versions. Update the version field in both:

    • tapo/Cargo.toml
    • tapo-py/pyproject.toml
  3. 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.X to the link definitions at the bottom of the file (right after the [Unreleased] link).
  4. Commit. Run /commit with message chore(tapo): release vX.X.X.

  5. Tag. Create an annotated git tag:

    git tag -a vX.X.X -m "vX.X.X"
    
  6. Push. Ask the user for confirmation, then:

    git push && git push origin vX.X.X
    
  7. 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 from CHANGELOG.md as 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
    )"
    

Read the full file on GitHub · 55 lines

Changes

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.

  1. 9d ago First seen · 55 lines · 31 tokens per session scan A 652dd8bf858f

Subscribe to this mod's changes

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.