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.
npx agentmods add agents/bottobot/touchdesigner-mcp-server/validate-changesgit clone --depth 1 https://github.com/bottobot/touchdesigner-mcp-serverWhat 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 | $0.00019 | $0.00213 |
| Opus 5 | $0.00010 | $0.00106 |
| Sonnet 5 | $0.00004 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
validate-changes 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.
What it actually says
Validate all recent changes to the TouchDesigner MCP Server at /home/robert/Documents/TD-MCP/touchdesigner-mcp-server. Tasks: (1) Run node --check on index.js and every file in tools/ to verify zero syntax errors. (2) Verify index.js properly registers all new tools: get_version_info, list_versions, get_experimental_techniques, search_experimental, get_glsl_pattern, get_operator_connections, get_network_template, get_experimental_build, list_experimental_builds. Count should now be 21 registered tools. (3) Validate all new JSON files in wiki/data/versions/ and wiki/data/experimental/ are valid JSON. (4) Confirm CHANGELOG.md has entries for all 4 streams. (5) If any issues are found, fix them immediately before proceeding. Report final tool count and any fixes applied.
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.
- 2d ago First seen · 7 lines · 0 tokens per session scan A b45d9e804544
validate-changes is an agent published in the GitHub repository bottobot/touchdesigner-mcp-server (76 stars, last pushed 13d ago), licensed MIT. It adds 19 tokens to every session and 213 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 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.
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.
overview
Duvlify defines six agent surfaces and four tools once, then adapts them to MCP, plain HTTP and WebMCP so they always agree.
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.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.