Borrowing it
Nothing to install: this file belongs to 8beeeaaat/touchdesigner-mcp. 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/8beeeaaat/touchdesigner-mcp/main/.claude/skills/prepare-release/SKILL.mdgit clone --depth 1 https://github.com/8beeeaaat/touchdesigner-mcpWrote 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/8beeeaaat/touchdesigner-mcp/prepare-release)<a href="https://agentmods.dev/skills/8beeeaaat/touchdesigner-mcp/prepare-release"><img src="https://agentmods.dev/badge/skills/8beeeaaat/touchdesigner-mcp/prepare-release.svg" alt="Measured on agentmods" 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.00149 | $0.01326 |
| Opus 5 | $0.00075 | $0.00663 |
| Sonnet 5 | $0.00030 | $0.00265 |
| Haiku 4.5 | $0.00015 | $0.00133 |
Grade A, and why
prepare-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 8d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare release
Cut a release for touchdesigner-mcp. The job has one non-obvious core: the
repo has two independent version axes, and npm version bumps both — the API
axis must be reverted when the release has no server/API contract change. Read
references/version-policy.md before touching any
version file.
Land the release via a development → main PR (historical flow; PR title is the
version, e.g. v1.4.13). Do not merge or publish — stop at the opened PR.
Step 0 — preflight
git fetch --tags
LAST_TAG=$(git describe --tags --abbrev=0) # e.g. v1.4.12
git log "$LAST_TAG"..HEAD --oneline # the unreleased commits
git diff "$LAST_TAG"..HEAD --stat # the unreleased surfaces
If the range is empty, there is nothing to release — stop and say so.
Step 1 — audit integration-test coverage first
Before writing anything, confirm the release diff is adequately tested. Invoke
the release-test-audit skill: it walks the API/MCP surface changes in the
unreleased range and reports coverage gaps. Resolve (or consciously waive) gaps
via the integration-test-guard skill before cutting the release. Don't
bump a release with an untested API/MCP surface change.
Step 2 — decide the two version axes
Read references/version-policy.md and decide, from the Step 0 diff:
- Package version — always bumps. Pick patch / minor / major from the change set (features → minor, fixes/deps → patch, breaking → major).
- MCP API version — bumps only if the diff changes the server/API
contract (
src/api/**, contract-changingsrc/features/tools/**ortd/modules/mcp/**,src/server/**,src/tdClient/**,src/transport/**). Otherwise it stays put and must be reverted afternpm version.
State the decision out loud before proceeding — it drives both the bump and the CHANGELOG wording.
Step 3 — write the CHANGELOG entry
Follow references/changelog-format.md. Group the Step 0 commits into Keep-a-Changelog sections, write impact-first prose, reference the merged PRs, and include the mandatory "Released version … across …" bullet whose last sentence records the Step 2 API-axis decision.
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.
- 8d ago First seen · 127 lines · 149 tokens per session scan A 26e3f7432959
prepare-release is a skill published in the GitHub repository 8beeeaaat/touchdesigner-mcp (519 stars, last pushed 1mo ago), licensed MIT. It adds 149 tokens to every session and 1,326 once invoked, about $0.0007 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
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry this project targets (npm, MCP Registry). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup…
release-management
Tag a commit, publish a GitHub release, and read, correct or withdraw the tags and releases already there.
release-versioning
Discipline for release classification, version bumps, and changelogs, Conventional Commits classify the release range, SemVer computes the version from those commits, Keep a Changelog renders the result. Use when the user asks to cut a release, bump a version, write a changelog, decide if a change is a…
hmem-release
Pre-publish checklist for hmem: skills synced, version bumped, tests green, nothing forgotten. Use before npm publish or when the user says 'release', 'publish', 'push a release', or 'neue Version'.
safe-deployment
Discipline for shipping changes reversibly, decouple deploy (code reaches production) from release (users see it) with feature flags, roll out progressively, and define the automated rollback trigger before shipping, not during the incident. Use when the user asks how to deploy a risky change, choose between…