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 dreamrec/TDPilot --skill popx-touchdesignergit clone --depth 1 https://github.com/dreamrec/TDPilotWrote 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/dreamrec/tdpilot/popx-touchdesigner)<a href="https://agentmods.dev/skills/dreamrec/tdpilot/popx-touchdesigner"><img src="https://agentmods.dev/badge/skills/dreamrec/tdpilot/popx-touchdesigner/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/dreamrec/tdpilot/popx-touchdesigner"><img src="https://agentmods.dev/badge/skills/dreamrec/tdpilot/popx-touchdesigner.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.00071 | $0.01372 |
| Opus 5 | $0.00036 | $0.00686 |
| Sonnet 5 | $0.00014 | $0.00274 |
| Haiku 4.5 | $0.00007 | $0.00137 |
Grade A, and why
popx-touchdesigner 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 9d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
POPX TouchDesigner
POPx is a paid plugin — its documentation is copyrighted and not distributed with TDPilot.
You must build the reference files locally from your own licensed copy (see references/BUILD.md).
This skill is backed by:
- A locally-generated reference catalog in
references/(user must build — seereferences/BUILD.md) - A live example loader in the open TouchDesigner project at
/EXAMPLE_LOADER - Build scripts in
scripts/for generating references from your own POPx installation
If you are modifying the live TouchDesigner project with td_ tools, also follow the tdpilot-core skill.
Quick Start
- Build references first if not done: see
references/BUILD.md. - Open
references/overview.md. - Run
python3 scripts/search_popx_refs.py "<query>"if the request is broad or ambiguous. - Open the smallest relevant reference file:
references/guides.mdreferences/operators-generators.mdreferences/operators-falloffs.mdreferences/operators-modifiers.mdreferences/operators-tools.mdreferences/operators-simulations.mdreferences/examples.md
- If exact wiring or working values matter, inspect the live example loader, not just the generated markdown.
Operator Workflow
Use the docs references for operator semantics and parameter intent.
- For generators, falloffs, modifiers, tools, or simulations, open the matching operator family file first.
- Use
references/catalog.jsononly throughscripts/search_popx_refs.py; do not load the JSON into context unless necessary. - Prefer operator pages over examples when the user asks how an operator works.
- Prefer examples over operator pages when the user asks for a known-good setup, working values, or a finished pattern to recreate.
Example Workflow
When the user refers to a shipped example or wants a POPX setup that already exists:
- Open
references/examples.mdand find the example entry. - Use the related docs listed there to understand the operator set involved.
- If you need exact values, inspect the live example inside TouchDesigner:
- Read
/EXAMPLE_LOADERparameters to confirm the example menu and current selection. - Set
/EXAMPLE_LOADERparameterExampleto the desired entry. - Pulse
/EXAMPLE_LOADER/exampleparameterenableexternaltoxpulseor pulse loaderReload. - Read
/EXAMPLE_LOADER/example/description. - Inspect
/EXAMPLE_LOADER/examplewithtd_get_nodes,td_get_params,td_get_connections, andtd_get_errors.
- Read
- Treat the loaded example as the source of truth for working values.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 130 lines · 71 tokens per session scan A ab2c53d2010d
popx-touchdesigner is a skill published in the GitHub repository dreamrec/TDPilot (11 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,372 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-31.
Other skills, from other repositories
tdmcp-kinect-wall-harp
Orchestrates the dedicated Kinect wall harp implementation team. Use whenever the user asks to build, implement, continue, fix, QA, document, or ship the Kinect wall harp, Kinect v2 wall-depth harp, FreenectTD depth-blob hand tracking, projected wall strings, pluck synth harp, or this feature's Layer 1…
tdmcp-pipeline
Orchestrates the tdmcp feature team end-to-end: design/wireframe → build → integrate → QA → release. Use whenever the user wants to build, implement, develop, ship, or add one or more tdmcp features/tools/effects/controls/AI-prompts for TouchDesigner, or to run them through a coordinated design→develop→QA→deploy…
td-trend-scout
Scout ONE external surface of the TouchDesigner community for what's HYPED in 2025-2026 that could become a tdmcp tool. Use when a td-trend-scout sub-agent is assigned a surface (community-showcase, tutorials, generative-ai, hardware-interactive, or vfx-aesthetics) during the tdmcp-hype-scout harness — produces…
tdmcp-raytk-integration
Plan and implement native RayTK (t3kt/raytk) raymarching/SDF toolkit integration into tdmcp — beyond the existing package-manager staging, into AI-driven RayTK operator (ROP) node graphs. Use whenever the user wants to build, plan, design, implement, continue, fix, QA, or ship RayTK support: create/wire RayTK ROPs, a…
tdmcp-artist-workflows
Build and refine TouchDesigner projects with tdmcp using context-first, visible, reversible workflows.
p5js
Use when users request: p5.js sketches, creative coding, generative art, interactive visualizations, canvas animations, browser-based visual art, data viz, shader effects, or any p5.js project.