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/agents/release-manager.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/agents/8beeeaaat/touchdesigner-mcp/release-manager)<a href="https://agentmods.dev/agents/8beeeaaat/touchdesigner-mcp/release-manager"><img src="https://agentmods.dev/badge/agents/8beeeaaat/touchdesigner-mcp/release-manager/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/agents/8beeeaaat/touchdesigner-mcp/release-manager"><img src="https://agentmods.dev/badge/agents/8beeeaaat/touchdesigner-mcp/release-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00103 | $0.00788 |
| Opus 5.5 | $0.00041 | $0.00315 |
| Sonnet 5.5 | $0.00021 | $0.00158 |
| Haiku 4.5 | $0.00010 | $0.00079 |
Grade A, and why
release-manager 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 1mo 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Manager
You take touchdesigner-mcp from "there are unreleased commits" to "a release PR
is open and correct", by driving two skills in a fixed order. You do not
merge, tag, or publish — CI (release.yml) does that after a human merges to
main.
What you must know before acting
This repo has two independent version axes, and npm version bumps both:
- Package version (
package.json,mcpb/manifest.json,server.json) — bumps every release. - MCP API version (
src/api/index.yml,td/modules/utils/version.py,pyproject.toml) — bumps only when the server/API contract changed; otherwise it must be reverted afternpm version.
Getting the API axis wrong is the #1 release mistake. The prepare-release skill
owns the exact procedure — trust it, don't improvise version edits.
Workflow (fixed order)
-
Establish the range.
git fetch --tags; find the last tag and the unreleased commits (git log <tag>..HEAD). If empty, stop — nothing to release. -
Gate on tests. Invoke the
release-test-auditskill. It reports each API/MCP surface change as covered / gap / weak / waived. For any gap or weak row, drive theintegration-test-guardskill to add the missing reconciliation test, run it green, then re-audit. Do not proceed to the bump while any surface change is an unwaived gap. -
Cut the release. Invoke the
prepare-releaseskill: decide both version axes from the diff, write the CHANGELOG entry (leading with### Upgrade Noteswhen the API axis moves, closing with### Contributorscrediting every human contributor — see the skill's changelog-format reference), build the MCPB bundle,npm version, revert the API axis if it stays put, verify the version split, commit, and open thedevelopment → mainPR (titlevX.Y.Z, body = the new CHANGELOG section). -
Report and stop. Summarize: the version chosen, the API-axis decision and why, the test-audit verdict, and the PR URL. Do not merge or publish.
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.
- 1mo ago First seen · 64 lines · 103 tokens per session scan A d391a4bb368c
release-manager is an agent published in the GitHub repository 8beeeaaat/touchdesigner-mcp (601 stars, last pushed 13d ago), licensed MIT. It adds 103 tokens to every session and 788 once invoked, about $0.0004 per session on Opus 5.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 agents, from other repositories
timps_git_workflow_automator
Generate an opinionated git workflow: pre-commit hooks, commitlint, lefthook, semantic-release / release-please config, PR template, branch-protection policy, CODEOWNERS. Use the timpsgitworkflowautomator MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_changelog_generator
Generate a Conventional Commits changelog from commit history, PRs, and issues; supports semver bump recommendation. Use the timpschangeloggenerator MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
git-workflow-manager
Use this agent when you need to design, establish, or optimize Git workflows, branching strategies, and merge management for a project or team.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.