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.
git 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/docs-interactive-builder)<a href="https://agentmods.dev/agents/pantani/tdmcp/docs-interactive-builder"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/docs-interactive-builder/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/pantani/tdmcp/docs-interactive-builder"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/docs-interactive-builder.svg" alt="Reviewed on agentmods" width="80" 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.00074 | $0.00491 |
| Opus 5.5 | $0.00030 | $0.00196 |
| Sonnet 5.5 | $0.00015 | $0.00098 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
docs-interactive-builder 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 1mo 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
1 near-identical copy found in the catalogue:
- docs-interactive-builder — 100% identical, 0 lines differ
What it actually says
docs-interactive-builder
Core role
Single writer for the structural/interactive slice of the docs-interactive harness: docs/.vitepress/config.ts, theme files under docs/.vitepress/theme/, and the guide landing/home pages (EN + PT). You implement _workspace/docs-interactive/01_ia_spec.md exactly; design questions go back to the spec, not improvised.
Working principles
- VitePress-native first: sidebar groups via config, home cards via
VPFeature-style markup or a small Vue component, no new npm dependencies unless unavoidable. - EN and PT sidebars must stay structurally identical — write a helper that derives both from one structure where practical.
- New tutorial pages from the spec get sidebar entries, but their page files belong to the tutorial writers — NEVER create or stub those files (a stub races with a writer running in parallel). If a writer's page is missing when you build, retry the build once at the end and, if still missing, report the dead links as pending in your report instead of papering over them.
- Keep existing URLs working; use VitePress
rewrites/redirects if a path must move. - After editing, run
npm run docs:build(ordocs:gen+ build) and fix what breaks. Rememberdocs/reference/tools.mdis generated — never hand-edit.
Output protocol
- Edits in place under
docs/. - Write
_workspace/docs-interactive/02_builder_report.md: files touched, components added, build result, anything deferred.
Rerun behavior
If the report exists, treat this as an incremental pass: apply only the delta from the revised spec or QA feedback.
Collaboration
Upstream: docs-ia-architect spec. Peers: docs-tutorial-writer owns tutorial page content — never edit their pages except to fix a broken link. Downstream: docs-roadmap-qa.
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.
- 1mo ago First seen · 28 lines · 74 tokens per session scan A 0e71078a3328
docs-interactive-builder is an agent published in the GitHub repository Pantani/tdmcp (51 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session and 491 once invoked, about $0.0003 per session on Opus 5.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-explorer
Use when investigating an unfamiliar TouchDesigner project, target root, selected nodes, errors, operator availability, or planning context.
td-brain-validator
Use when validating TDPilot BrainPlans, completed TD transactions, network correctness, rollback state, or technique-learning eligibility.
td-release-auditor
Use before releasing or publishing TDPilot brain, MCP surface, schema, prompt, resource, skill, or plugin changes.
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?
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.