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 skills add 8beeeaaat/touchdesigner-mcp --skill perfgit 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/skills/8beeeaaat/touchdesigner-mcp/perf)<a href="https://agentmods.dev/skills/8beeeaaat/touchdesigner-mcp/perf"><img src="https://agentmods.dev/badge/skills/8beeeaaat/touchdesigner-mcp/perf/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/skills/8beeeaaat/touchdesigner-mcp/perf"><img src="https://agentmods.dev/badge/skills/8beeeaaat/touchdesigner-mcp/perf.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.00100 | $0.01302 |
| Opus 5.5 | $0.00040 | $0.00521 |
| Sonnet 5.5 | $0.00020 | $0.00260 |
| Haiku 4.5 | $0.00010 | $0.00130 |
Grade A, and why
perf 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 25d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TD Perf
Diagnose TouchDesigner performance bottlenecks by measuring per-operator cook time and correlating the worst offenders with known heavy patterns.
Workflow
-
Explain up front that real measurement requires running a script via
execute_python_script— the permission prompt that may follow is expected, not a malfunction. -
Call
get_td_infoto confirm TouchDesigner is reachable before doing anything else; if it fails, point the user at/touchdesigner:setupinstead of proceeding. -
Resolve
rootto theroot-pathargument if given, otherwise/project1if it exists, else/(a project launched by opening the tox as a document has no/project1). -
With the user's consent, run a measurement script through
execute_python_scriptwithdetailLevel: "detailed"so the complete ranking is returned rather than the summary formatter's 500-character preview. Collect the resolved root and its descendants:findChildren()walks the whole subtree when called with no arguments (maxDepthlimits it, whiledepthis an exact-match filter, not a limit), but it never returns the operator it was called on — that operator is depth 0, andfindChildren(depth=0)is empty. Leave the root out and aroot-pathnaming a single TOP measures nothing at all, while a COMP's own cook time goes missing fromtotalCookTime, and for each operator record itspath,name,opType, andcookTime(skipping operators wherecookTimeisn't a meaningful attribute rather than erroring out). Sort the collected results bycookTimedescending and keep roughly the top 20 — but return the number of operators measured and the sum of all their cook times alongside that slice. The slice is the only thing that survives the call, so a denominator left behind cannot be recovered afterwards. For example:root = "/project1" # the path resolved in step 3 root_op = op(root) results = [] for child in [root_op, *root_op.findChildren()]: ct = getattr(child, "cookTime", None) if ct is not None: results.append( { "path": child.path, "name": child.name, "opType": getattr(child, "OPType", ""), "cookTime": ct, } ) results.sort(key=lambda r: r["cookTime"], reverse=True) result = { "measuredCount": len(results), "totalCookTime": sum(r["cookTime"] for r in results), "top": results[:20], }
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.
- 25d ago First seen · 63 lines · 100 tokens per session scan A 595f412bc6b1
perf is a skill published in the GitHub repository 8beeeaaat/touchdesigner-mcp (582 stars, last pushed 4d ago), licensed MIT. It adds 100 tokens to every session and 1,302 once invoked, about $0.0004 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-09-21.
Other skills, from other repositories
operator-gotchas
MUST READ before wiring a TOP, CHOP, MAT, DAT, light, camera or instancing chain you have not built before: the parameter names TD abbreviates, the defaults that silently do the wrong thing, and the input-order rules, per operator, verified on TD 2025.33230. Pair with describeoptype.
debug-operator
TRIGGER when operator errors appear or user reports broken behavior. Systematic diagnosis workflow.
chrome-devtools-cli
Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).
n8n-validation-expert
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities.…