tapo: Skill for Claude Code

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

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

A release checklist for the tapo-mcp Rust package, an MCP server for Tapo devices. It covers version updates, changelog changes, commits, tags, publishing steps, and the GitHub release.

In plain words
What is it for?
Use it to prepare and release a new tapo-mcp version, including updating package metadata and creating the related Git tag and GitHub release.
Why use it?
It reduces the chance of missing a file or release step when shipping a new version of tapo-mcp.

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-mcp/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-mcp

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/mihai-dinculescu/tapo/release-mcp"><img src="https://agentmods.dev/badge/skills/mihai-dinculescu/tapo/release-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 572 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.00028 $0.00572
Opus 5 $0.00014 $0.00286
Sonnet 5 $0.00006 $0.00114
Haiku 4.5 $0.00003 $0.00057

Measured 11d ago against content hash 5600c92f5365, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

release-mcp 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 11d 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-mcp/SKILL.md · 45 lines

What it actually says

Release tapo-mcp

Release a new version of the tapo-mcp crate.

Steps

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

  2. Bump the version. Update the version field in tapo-mcp/Cargo.toml and both version and packages[0].identifier in tapo-mcp/server.json.

  3. Update changelog. In CHANGELOG.md:

    • Replace the heading ## [MCP Unreleased][Unreleased] with ## [MCP vX.X.X][tapo-mcp-vX.X.X] - YYYY-MM-DD (use the current date).
    • Insert a new empty ## [MCP Unreleased][Unreleased] section immediately above the newly versioned section.
    • Add a link reference [tapo-mcp-vX.X.X]: https://github.com/mihai-dinculescu/tapo/tree/tapo-mcp-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-mcp): release vX.X.X.

  5. Tag. Create an annotated git tag:

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

    git push && git push origin tapo-mcp-vX.X.X
    
  7. Create GitHub release. Ask the user for confirmation. Use the content under the ## [MCP vX.X.X][tapo-mcp-vX.X.X] heading from CHANGELOG.md as the release body, followed by a full changelog comparison link. The previous version (vP.P.P) is the tapo-mcp tag before this release:

    gh release create tapo-mcp-vX.X.X --title "Tapo MCP vX.X.X" --notes "$(cat <<'EOF'
    <changelog content here>
    
    **Full Changelog**: https://github.com/mihai-dinculescu/tapo/compare/tapo-mcp-vP.P.P...tapo-mcp-vX.X.X
    EOF
    )"
    
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. 11d ago First seen · 45 lines · 28 tokens per session scan A 5600c92f5365

Subscribe to this mod's changes

release-mcp is a skill published in the GitHub repository mihai-dinculescu/tapo (799 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 572 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

release

Evaluate readiness and publish to crates.io.

yologdev/yoyo-evolve · 9 tokens

update-v8-version

Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.

openinterpreter/openinterpreter · 86 tokens

cargo-release

PM-invocable protocol for Cargo publish and release operations in the trusty-tools Rust monorepo: semver rules, 10-step release sequence, macOS codesign safety, and cross-crate dependency ordering.

bobmatnyc/claude-mpm-skills · 45 tokens

rust-release

Plan and execute Rust release engineering. Use when: publishing a crate, setting up release automation, cross-compiling binaries. Do not use: for version bumping alone, local build setup.

woliveiras/geremmyas · 41 tokens

cargo-publish

Operate the socket-release crates.io flow - the cargo staged model (dry-run default), trusted publishing via OIDC under the cargo-publish environment, index-propagation waits, and yank-as-rollback. Use when publishing a Rust crate in a repo carrying scripts/socket-release/.

SocketDev/sauce · 59 tokens

jackin-release

Use only when the user explicitly requests this skill. Cuts a jackin❯ release — runs the readiness gates, writes the changelog, recommends a version, then executes cargo release on explicit operator confirmation.

jackin-project/jackin-dev · 45 tokens