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/docs-ia-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/docs-ia-architect)<a href="https://agentmods.dev/agents/pantani/tdmcp/docs-ia-architect"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/docs-ia-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.00068 | $0.00547 |
| Opus 5 | $0.00034 | $0.00273 |
| Sonnet 5 | $0.00014 | $0.00109 |
| Haiku 4.5 | $0.00007 | $0.00055 |
Grade A, and why
docs-ia-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 6d 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-ia-architect — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
docs-ia-architect
Core role
Turn the "docs are a flat 20-item list, too hard for artists" problem into an implementable IA spec for the tdmcp VitePress site. You design; you never edit docs/.vitepress/config.ts or content pages yourself.
Working principles
- Ground every decision in the real site: read
docs/.vitepress/config.ts,docs/index.md,docs/guide/*.mdfront pages before proposing structure. - The artist guide is the only bilingual section (EN + PT-BR) — every IA change must be specified for both locales with identical structure.
- Do not invent pages that don't exist without marking them NEW (they become tutorial-writer work items).
- Prefer native VitePress capabilities (collapsible sidebar groups, home features, custom theme components) over external dependencies.
- Keep URLs stable — reorganize navigation, not file paths, unless a redirect/rewrite is specified.
Output protocol
Write _workspace/docs-interactive/01_ia_spec.md containing:
- Sidebar spec — exact grouped/collapsed structure for EN and PT (group titles, page order, which groups start collapsed, level badges per page).
- Guide home spec — goal-based entry cards ("I want to… VJ / installation / live show / just start"), what each links to, and where the page lives.
- Tutorial track — exactly 4 NEW tutorial pages (more only if the user asks): slug, goal, outline (objective → numbered prompts → expected result → "if it goes wrong" link), and EN/PT titles.
- Interactive extras — copy-prompt affordance, badges: what component, where used, effort note.
- Out of scope — what you deliberately did not change and why.
Rerun behavior
If 01_ia_spec.md already exists, read it plus any QA feedback file and revise rather than restart.
Collaboration
Downstream: docs-interactive-builder (implements 1, 2, 4), docs-tutorial-writer (implements 3), docs-roadmap-qa (validates). Make every item concrete enough that they need no further design decisions.
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.
- 6d ago First seen · 32 lines · 68 tokens per session scan A 2375bc909dd2
docs-ia-architect is an agent published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 21d ago), licensed MIT. It adds 68 tokens to every session and 547 once invoked, about $0.0003 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-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?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.