touchdesigner-mcp-server: Agent for Claude Code

.claude/agents/validate-version-system.md

validate-version-system is an agent for Claude Code from bottobot/touchdesigner-mcp-server. It costs 14 tokens per session (306 once invoked), scanned A, original, MIT.

A validation agent for checking a version-specific TouchDesigner MCP Server implementation. TouchDesigner is software for creating interactive media, and MCP Server refers to the project’s tool server.

In plain words
What is it for?
Use it to run JavaScript syntax checks, validate compatibility files, inspect tool registrations, and fix any issues it finds.
Why use it?
It checks whether the implementation and its JSON data files are syntactically valid and whether expected version features are present.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is bottobot/touchdesigner-mcp-server's own configuration. It tells Claude Code how to work on touchdesigner-mcp-server 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 touchdesigner-mcp-server configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/robert/Documents/TD-MCP/touchdesigner-mcp-server.

Reuse

Borrowing it

Nothing to install: this file belongs to bottobot/touchdesigner-mcp-server. 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/bottobot/touchdesigner-mcp-server/main/.claude/agents/validate-version-system.md
Clone the repo
git clone --depth 1 https://github.com/bottobot/touchdesigner-mcp-server

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 validate-version-system

README.md
[![agentmods](https://agentmods.dev/badge/agents/bottobot/touchdesigner-mcp-server/validate-version-system/github.svg)](https://agentmods.dev/agents/bottobot/touchdesigner-mcp-server/validate-version-system)
Your own site
<a href="https://agentmods.dev/agents/bottobot/touchdesigner-mcp-server/validate-version-system"><img src="https://agentmods.dev/badge/agents/bottobot/touchdesigner-mcp-server/validate-version-system/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 validate-version-system

Your own site · 80×15
<a href="https://agentmods.dev/agents/bottobot/touchdesigner-mcp-server/validate-version-system"><img src="https://agentmods.dev/badge/agents/bottobot/touchdesigner-mcp-server/validate-version-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 306 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.
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.00014 $0.00306
Opus 5.5 $0.00006 $0.00122
Sonnet 5.5 $0.00003 $0.00061
Haiku 4.5 $0.00001 $0.00031

Measured 1mo ago against content hash 5aefe02df1bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

validate-version-system 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.

.claude/agents/validate-version-system.md · 27 lines

What it actually says

You are validating the version-specific system implementation in the TouchDesigner MCP Server.

Project location: /home/robert/Documents/TD-MCP/touchdesigner-mcp-server

Tasks:

  1. Run: node --check tools/get_version_info.js
  2. Run: node --check tools/list_versions.js
  3. Run: node --check tools/search_operators.js
  4. Run: node --check tools/get_operator.js
  5. Run: node --check tools/search_python_api.js
  6. Run: node --check tools/get_python_api.js
  7. Run: node --check index.js
  8. Run: node --check wiki/utils/version-filter.js (if it exists)
  9. Verify these JSON files are valid: node -e "JSON.parse(require('fs').readFileSync('wiki/data/versions/version-manifest.json','utf8')); console.log('valid')"
  10. Verify operator-compatibility.json and python-api-compatibility.json are valid JSON
  11. Check that index.js contains registrations for 'get_version_info' and 'list_versions'
  12. Verify at least one operator in /wiki/data/processed/ has a versionSupport field

Fix ANY issues found before completing. If a file is missing, create a minimal valid version.

Report: List of all version-related files created/modified, validation results, fixes applied.

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. 1mo ago First seen · 27 lines · 14 tokens per session scan A 5aefe02df1bc

Subscribe to this mod's changes

validate-version-system is an agent published in the GitHub repository bottobot/touchdesigner-mcp-server (80 stars, last pushed 28d ago), licensed MIT. It adds 14 tokens to every session and 306 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

evidence-based-investigator

Investigates codebase issues by gathering concrete evidence — file paths, line numbers, code snippets, error messages, git history, and test coverage. Use when thorough, multi-angle research into a bug, failure, or unexpected behavior is needed. Does not trace runtime data flow across modules — use behavioral-analyst.…

testdouble/han · 85 tokens

edge-case-explorer

Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…

testdouble/han · 135 tokens

test-failure-analyst

Reads test output and source to explain why a test fails. Use after a failing test run.

Goldziher/ai-rulez · 26 tokens

SWE

Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.

archubbuck/workspace-architect · 23 tokens

debugger

Bug-fix specialist — root-cause via systematic-debugging, not full lifecycle orchestration.

lugassawan/swe-workbench · 22 tokens

distributed-test-engineer

Diagnoses and fixes distributed system test failures in NATS JetStream, pytest-asyncio fixture scoping, MCP transport lifecycles, and asyncio event loop conflicts. Use when hosted NATS E2E tests hang, connection lifecycle bugs appear, or fixture deadlocks occur.

punt-labs/biff · 61 tokens