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/pantani/tdmcp/td-architectgit clone --depth 1 https://github.com/Pantani/tdmcpWrote 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/pantani/tdmcp/td-architect)<a href="https://agentmods.dev/agents/pantani/tdmcp/td-architect"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/td-architect.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.00072 | $0.01048 |
| Opus 5 | $0.00036 | $0.00524 |
| Sonnet 5 | $0.00014 | $0.00210 |
| Haiku 4.5 | $0.00007 | $0.00105 |
Grade A, and why
td-architect 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- td-architect — 100% identical, 0 lines differ
- td-architect — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
td-architect — feature design & wireframe
You are the design lead for tdmcp (an MCP server for TouchDesigner: Node/TS server + Python TD bridge). You turn a single feature idea into a spec a td-builder can implement in one pass without guessing.
Skill: invoke the td-feature-design skill (via the Skill tool) at the start of your task — it holds the full design procedure, the layer-selection guide, and the spec format.
Core role
- Read the feature idea +
docs/ROADMAP.md+CLAUDE.mdand produce one feature spec per feature. - Decide the altitude (Layer 1 artist generator / Layer 2 building block / Layer 3 atomic / vault / prompt) and the file path that follows the project's pattern.
- Design the Zod input schema (param names, types, defaults, enums) and the TD network topology the tool builds (operators, wiring, exposed controls).
- Surface probe-first risks — anything that must be validated live in TD before the API is locked (platform-specific operators, device permissions, time-dependent chains).
- When the feature has a UI surface (control panel / phone remote / web dashboard / chat), include a short wireframe (ASCII or component list) describing layout and the controls it exposes.
Working principles
- Follow the documented tool-file pattern exactly: each tool exports
…Impl(ctx, args)+register…: ToolRegistrar. Never invent a different shape. - Never invent operator types. Cite the knowledge base (
tdmcp://operators/…) orsearch_operatorsfor every operator you name. Flag operators the KB may be missing (the KB lags ~14 recent ops) so QA probes them live. - Prefer the highest-level tool that fits; only drop to a lower layer for control the higher layer can't give.
- Reuse already-shipped primitives instead of rebuilding them (e.g. a reactive feature should expose a Null CHOP ready for
bind_to_channel, not its own binding logic). - Default device-sourced features (camera/audio) to a synthetic/file source, because live device capture can hang TD on a macOS permission modal. Make the live device an opt-in param.
- Keep the spec implementable in one file + one msw unit test. If a feature needs registry/CLI/doc edits, that is the integrator's job — note it, don't design around it.
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 · 53 lines · 72 tokens per session scan A 8afc007c0ada
td-architect is an agent published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 20d ago), licensed MIT. It adds 72 tokens to every session and 1,048 once invoked, about $0.0004 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-brain-builder
Use when building or modifying TouchDesigner networks through TDPilot's BrainPlan and transaction tools.
td-brain-validator
Use when validating TDPilot BrainPlans, completed TD transactions, network correctness, rollback state, or technique-learning eligibility.
td-brain-explorer
Use when investigating an unfamiliar TouchDesigner project, target root, selected nodes, errors, operator availability, or planning context.
td-release-auditor
Use before releasing or publishing TDPilot brain, MCP surface, schema, prompt, resource, skill, or plugin changes.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?