agentmods.dev

td-explain-patch

A read-only guide to understanding an open TouchDesigner project. TouchDesigner is a visual tool where connected nodes process images, data, and effects.

In plain words
What is it for?
Use it to trace sources through processing to the final output, inspect project problems, find performance hotspots, and identify small improvements.
Why use it?
It turns an unfamiliar node network into a plain-language map and points out errors, broken links, unused parts, and slow operations.

Command

11 1mo ago A scan 21 tokens original MIT
View the source file dreamrec/TDPilot
Install

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.

agentmods
npx agentmods add commands/dreamrec/tdpilot/td-explain-patch
Clone the repo
git clone --depth 1 https://github.com/dreamrec/TDPilot
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 371 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00021 $0.00371
Opus 5 $0.00010 $0.00186
Sonnet 5 $0.00004 $0.00074
Haiku 4.5 $0.00002 $0.00037

Measured 2d ago against content hash da33bef7755a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

td-explain-patch 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 2d 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.

commands/td-explain-patch.md · 30 lines

What it actually says

Give the user a clear, honest map of the TouchDesigner project they already have open. This is strictly read-only — do not create, modify, or delete anything.

  1. Verify the connection with td_get_info (project name, build, FPS).
  2. Audit. Call td_audit_project for the structural overview, then td_get_nodes on /project1 (and the 2-3 largest child COMPs) to map the real network. Use td_get_errors recursively for problems and td_cooking_info for the performance hot spots.
  3. Identify the spine. Find the main signal path(s): sources → processing → output (final TOP / output window). Note dead ends and orphaned nodes.
  4. Report in this shape, concise and jargon-light:
    • What this project is: one-paragraph read of its purpose and style.
    • Signal flow: the main chain(s), named node by node.
    • Problems found: errors, warnings, broken references — each with the one-line fix.
    • Performance: the top cook-time offenders and whether they matter at the project's FPS.
    • Three quick wins: concrete, small improvements you could make on request (each one tool call away — but do NOT do them now).
  5. Offer next steps: "want me to fix any of these?" plus /td-snapshot before any edits.

If the project is empty or nearly empty, say so and point to /td-first-wow instead of padding an empty audit.

Changes

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.

  1. 2d ago First seen · 30 lines · 21 tokens per session scan A da33bef7755a

Subscribe to this mod's changes

td-explain-patch is a command published in the GitHub repository dreamrec/TDPilot (11 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 371 once invoked, about $0.0001 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.

Creative and mediaPlanningaiaudio-reactiveclaudeclaude-codecreative-codinggenerative-art
Related

Other commands, from other repositories

develop-image-prompt.eval

Generates a detailed image generation prompt from a document or content description. Good output: a prompt that is specific, visual, non-abstract, includes style/composition/lighting guidance, and is calibrated to the specified dimensions and style options.

davistroy/claude-marketplace · 0 tokens

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

constitution

Create or update the project constitution from interactive or provided principle inputs.

github/spec-kit · 13 tokens