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 instructions/8beeeaaat/touchdesigner-mcp/agents-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/instructions/8beeeaaat/touchdesigner-mcp/agents-md)<a href="https://agentmods.dev/instructions/8beeeaaat/touchdesigner-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/8beeeaaat/touchdesigner-mcp/agents-md.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 | $0.00616 | $0.00616 |
| Opus 5 | $0.00308 | $0.00308 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
touchdesigner-mcp AGENTS.md 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 5d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/ contains the TypeScript MCP server: shared logic is in core/, MCP features in features/, transport code in transport/, and TouchDesigner communication in tdClient/. The OpenAPI contract starts at src/api/index.yml. TouchDesigner-side Python, templates, generated artifacts, and .tox components live in td/. Tests belong in tests/unit/ or tests/integration/, documentation in docs/, and media in assets/. Treat dist/, src/gen/, and td/modules/td_server/ as generated output; edit their source schemas or templates instead.
Build, Test, and Development Commands
npm installinstalls Node dependencies.npm run buildregenerates code, compiles TypeScript, and copies runtime templates.make buildperforms the Docker-based TouchDesigner module build.npm run devopens the MCP Inspector against the built stdio server.npm run httpstarts HTTP mode on127.0.0.1:6280, targeting TouchDesigner on9981.npm test,npm run test:unit, andnpm run test:integrationrun all or scoped Vitest suites.npm run coveragewrites V8 reports;npm run lintruns all static checks.npm run genrefreshes OpenAPI, Python handler, and TypeScript client output.
Coding Style & Naming Conventions
Use ESM TypeScript, tabs, and double quotes; let Biome organize imports. Use camelCase for files and functions, PascalCase for types, and generally kebab-case for directories. Python targets 3.9; Ruff enforces tabs, double quotes, and an 88-character line length. Run npm run format for automatic fixes. Keep changes focused.
Testing Guidelines
Name tests *.test.ts and place them in the appropriate unit or integration directory. Use Vitest globals and vi.mock or in-memory fakes. Add regression coverage for bug fixes, especially compatibility, transport, and TouchDesigner client changes. Run the narrow suite while developing, then npm test and npm run lint before submitting.
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.
- 5d ago First seen · 33 lines · 616 tokens per session scan A 9bda0f5590fd
touchdesigner-mcp AGENTS.md is an instructions file published in the GitHub repository 8beeeaaat/touchdesigner-mcp (515 stars, last pushed 27d ago), licensed MIT. It adds 616 tokens to every session, about $0.0031 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 instructions, from other repositories
Embody CLAUDE.md
Claude Code instructions for dylanroscover/Embody, covering embody + envoy, project overview, critical rules, approach guidelines and project structure.
Embody AGENTS.md
AGENTS.md instructions for dylanroscover/Embody, covering embody + envoy - ai instructions, critical rules, td python rules, network layout rules and mcp server safety rules.
blockrun-mcp AGENTS.md
AGENTS.md instructions for BlockRunAI/blockrun-mcp, covering blockrun mcp, commands, project structure, key dependencies and install in codex.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
intervals-icu-mcp CLAUDE.md
Instructions for hhopke/intervals-icu-mcp, covering claude.md, project overview, development commands, architecture (quick reference) and tool categories.
ai-toolkit AGENTS.md
AGENTS.md instructions for pipefy/ai-toolkit, covering repository guidelines, documentation map, project structure, import namespace migration: pipefysdk → pipefy and src/pipefysdk/init.py (transitional shim).