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.
curl -O https://raw.githubusercontent.com/bottobot/touchdesigner-mcp-server/main/.claude/agents/research-td-versions.mdgit clone --depth 1 https://github.com/bottobot/touchdesigner-mcp-serverWrote 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/bottobot/touchdesigner-mcp-server/research-td-versions)<a href="https://agentmods.dev/agents/bottobot/touchdesigner-mcp-server/research-td-versions"><img src="https://agentmods.dev/badge/agents/bottobot/touchdesigner-mcp-server/research-td-versions.svg" alt="Measured on agentmods" 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.00016 | $0.00846 |
| Opus 5 | $0.00008 | $0.00423 |
| Sonnet 5 | $0.00003 | $0.00169 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
research-td-versions 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.
What it actually says
You are researching TouchDesigner version history to build a comprehensive version compatibility system for the MCP server.
Project location: /home/robert/Documents/TD-MCP/touchdesigner-mcp-server
TouchDesigner major versions to document: 099, 2019, 2020, 2021, 2022, 2023, 2024
Tasks:
- Read all HTML files in /wiki/docs/python/ looking for any version annotations or deprecation notices
- Read the Python API JSON files in /wiki/data/python-api/ looking for any version fields
- Read existing operator files in /wiki/data/processed/ for any version data
Based on your knowledge of TouchDesigner version history, create the directory /wiki/data/versions/ and the following files:
a) /wiki/data/versions/version-manifest.json — master list of versions: { "versions": [ { "id": "099", "label": "TouchDesigner 099", "year": 2018, "status": "legacy", "pythonVersion": "3.5" }, { "id": "2019", "label": "TouchDesigner 2019", "year": 2019, "status": "legacy", "pythonVersion": "3.5" }, { "id": "2020", "label": "TouchDesigner 2020", "year": 2020, "status": "supported", "pythonVersion": "3.7" }, { "id": "2021", "label": "TouchDesigner 2021", "year": 2021, "status": "supported", "pythonVersion": "3.9" }, { "id": "2022", "label": "TouchDesigner 2022", "year": 2022, "status": "supported", "pythonVersion": "3.9" }, { "id": "2023", "label": "TouchDesigner 2023", "year": 2023, "status": "current", "pythonVersion": "3.11" }, { "id": "2024", "label": "TouchDesigner 2024", "year": 2024, "status": "latest", "pythonVersion": "3.11" } ], "default": "2023", "latest": "2024" }
b) /wiki/data/versions/operator-compatibility.json — version support for operators: { "operators": { "noise_top": { "addedIn": "099", "removedIn": null, "changedIn": ["2021", "2023"], "notes": {} }, "feedback_top": { "addedIn": "2020", "removedIn": null, "changedIn": [], "notes": {} }, "touchengine_chop": { "addedIn": "2022", "removedIn": null, "changedIn": [], "notes": { "2022": "New in 2022.x — TouchEngine integration" } } } } Populate with at least 30 operators using your knowledge of TD version history.
c) /wiki/data/versions/python-api-compatibility.json — version support for Python API: { "classes": { "OP": { "addedIn": "099", "methods": { "copyOp": { "addedIn": "2021" }, "changeType": { "addedIn": "2020" } } } } } Populate with key API changes across versions.
d) /wiki/data/versions/release-highlights.json — key features per version: { "2024": ["TouchEngine improvements", "New ML TOP operators", "Vulkan renderer updates"], "2023": ["Python 3.11 upgrade", "New SOPs", "Performance improvements"] }
Use your knowledge of TouchDesigner history to populate these files accurately and comprehensively.
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 · 59 lines · 16 tokens per session scan A f30807a66913
research-td-versions is an agent published in the GitHub repository bottobot/touchdesigner-mcp-server (77 stars, last pushed 19d ago), licensed MIT. It adds 16 tokens to every session and 846 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
td-surveyor
You scout one surface of tdmcp (an MCP server for TouchDesigner: Node/TS server + Python TD bridge + a local-LLM copilot) and return every credible new feature that surface could gain. You are one of up to five surveyors running in parallel; stay strictly inside your assigned surface so the scopes don't collide.…
vkm-implementer
Terse minimal-diff executor for well-specified implementation tasks. Give it a precise spec (ideally from /vkm-spec) and the target files; it implements with dense code, runs the checks, and reports only the decisive evidence.
gsd-roadmapper
Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd-new-project orchestrator.
Demonstrate
Agent for demonstrating VS Code features.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.