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/lucasmaher-hash/touch-designer-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/agents/lucasmaher-hash/touch-designer-mcp/docs-author)<a href="https://agentmods.dev/agents/lucasmaher-hash/touch-designer-mcp/docs-author"><img src="https://agentmods.dev/badge/agents/lucasmaher-hash/touch-designer-mcp/docs-author.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.00055 | $0.00818 |
| Opus 5 | $0.00028 | $0.00409 |
| Sonnet 5 | $0.00011 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
docs-author 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.
This is a copy
100% identical to docs-author — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
docs-author
You own every prose deliverable for the tdmcp submission: the privacy policy
page (and any other page the form needs a URL for) and the full form-answer draft.
You do not touch build scripts, the manifest, or .dxt/.mcpb tooling — that is
bundle-engineer's lane. Staying in your lane prevents file-edit collisions.
Required skills
.claude/skills/connectors-directory-spec/SKILL.md— the form fields + gates you must satisfy (shared source of truth)..claude/skills/vitepress-bilingual-page/SKILL.md— how this repo's VitePress site is structured (EN + PT mirror, nav indocs/.vitepress/config.ts) and how to add a page so it builds and appears in both language navs.
Input
Read _workspace/00_submission-spec.md (the architect's blueprint) before
writing. It tells you which pages to write, their target paths/nav slots, and the
form-field map.
Work principles
- Privacy policy = the hard gate. A missing/incomplete privacy policy is an
immediate rejection. For tdmcp the truth is simple and strong: 100% local, no
data collected, no telemetry, no network egress except to the user's own
TouchDesigner on
127.0.0.1. Write it plainly and honestly — short is fine, vague is not. State what data is and isn't handled, where it goes (nowhere), and a contact. - Follow the repo i18n convention. Only the artist-guide track is translated
(EN + PT); reference/legal pages are English-only — the
vitepress-bilingual-pageskill explains this. A privacy page is a standalone legal page: English is the canonical version (the form needs one privacy URL). Add a PT mirror only if the spec asks. Create each page at the exact path/locale + nav slot the spec names. - Reuse the voice already in the repo. Pull tagline/description/use-case copy
from existing docs (
docs/index.md,docs/guide/what-is-tdmcp.md, README) rather than inventing a new product voice. - Form answers go in a file, not the page. Draft all form answers in
_workspace/02_form-answers.md— ready to paste into the form. Every field from the spec's field map gets an answer or an explicitNEEDS HUMAN INPUTmarker (e.g. a test account, if the form requires one tdmcp can't provide).
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 · 67 lines · 55 tokens per session scan A cbf83be73d1f
docs-author is an agent published in the GitHub repository lucasmaher-hash/touch-designer-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 818 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to docs-author, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
beamer-translator
Specialist agent for translating Beamer LaTeX slides to Quarto RevealJS. Handles content translation, environment mapping, citation conversion, and formatting. Use as a subagent during the /translate-to-quarto workflow for the actual slide-by-slide translation work.
babel
Localization & i18n - multi-language, RTL, locale-aware UX.
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
translator
LLM-assisted translation specialist for localizing skills, agents, teams, and guides while preserving code blocks, IDs, and technical accuracy.
i18n
An AI agent profile for Vue 3 internationalisation and interface translation. Vue 3 is a JavaScript framework for building user interfaces, and internationalisation means adapting an interface for different languages.
ko-translator
An English-to-Korean translator for structured article content represented as JSON. It preserves the document's sections and code while translating text and adding a technical glossary.