agentmods.dev

validate-version-system

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

76 +1 13d ago A scan 14 tokens original MIT
View the source file bottobot/touchdesigner-mcp-server
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/bottobot/touchdesigner-mcp-server/validate-version-system
Clone the repo
git clone --depth 1 https://github.com/bottobot/touchdesigner-mcp-server

Made for: Claude Code.

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. Scan, not verified.
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 $0.00014 $0.00306
Opus 5 $0.00007 $0.00153
Sonnet 5 $0.00003 $0.00061
Haiku 4.5 $0.00001 $0.00031

Measured 2d ago against content hash 5aefe02df1bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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. 2d 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 (76 stars, last pushed 13d ago), licensed MIT. It adds 14 tokens to every session and 306 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.

DebuggingTestingcodiumderivativedocumentationmcpmodel-context-protocoloperators
Related

Other agents, from other repositories

retrieval

Two retrieval backends: a lexical index built at compile time that needs no account, and Cloudflare AI Search for hybrid semantic search when you want it.

DuvInc/duvlify · 31 tokens

discovery

How an agent finds these surfaces without being told: the API catalog, DNS-based discovery, an agent-skills index, and the places people actually look.

DuvInc/duvlify · 31 tokens

overview

Duvlify defines six agent surfaces and four tools once, then adapts them to MCP, plain HTTP and WebMCP so they always agree.

DuvInc/duvlify · 30 tokens

mcp

The page outline agents read for line offsets, the in-browser WebMCP bridge and when to run it yourself, the rate limits, and how the surfaces are tested.

DuvInc/duvlify · 34 tokens

domain

How the engineering skills should consume this repo's domain documentation when exploring the codebase.

barateza/mcp-plesk-dev-docs · 0 tokens

issue-tracker

Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.

barateza/mcp-plesk-dev-docs · 0 tokens