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-mcp/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-mcp)<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.
<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>- 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.00028 | $0.00572 |
| Opus 5 | $0.00014 | $0.00286 |
| Sonnet 5 | $0.00006 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
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.
What it actually says
Release tapo-mcp
Release a new version of the tapo-mcp crate.
Steps
-
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. -
Bump the version. Update the
versionfield intapo-mcp/Cargo.tomland bothversionandpackages[0].identifierintapo-mcp/server.json. -
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.Xto the link definitions at the bottom of the file (right after the[Unreleased]link).
- Replace the heading
-
Commit. Run
/commitwith messagechore(tapo-mcp): release vX.X.X. -
Tag. Create an annotated git tag:
git tag -a tapo-mcp-vX.X.X -m "tapo-mcp-vX.X.X" -
Push. Ask the user for confirmation, then:
git push && git push origin tapo-mcp-vX.X.X -
Create GitHub release. Ask the user for confirmation. Use the content under the
## [MCP vX.X.X][tapo-mcp-vX.X.X]heading fromCHANGELOG.mdas 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 )"
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.
- 11d ago First seen · 45 lines · 28 tokens per session scan A 5600c92f5365
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.
Other skills, from other repositories
release
Evaluate readiness and publish to crates.io.
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.
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.
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.
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/.
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.