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 commands/dreamrec/tdpilot/td-snapshotgit 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/commands/dreamrec/tdpilot/td-snapshot)<a href="https://agentmods.dev/commands/dreamrec/tdpilot/td-snapshot"><img src="https://agentmods.dev/badge/commands/dreamrec/tdpilot/td-snapshot.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 | $0.00011 | $0.00147 |
| Opus 5 | $0.00005 | $0.00073 |
| Sonnet 5 | $0.00002 | $0.00029 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
td-snapshot 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 5d 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.
What it actually says
Use td_snapshot_scene to create a named snapshot of the current TouchDesigner
state. This captures node structure, parameters, and content so the scene can be
restored with td_restore_snapshot if a subsequent edit goes wrong.
Recommended workflow:
- Name the snapshot something descriptive (e.g. "pre-refactor", "before-param-bounds").
- Confirm via
td_list_snapshotsthat it was written. - Proceed with the edit.
- If the edit is bad, call
td_restore_snapshotwith that name.
This is cheaper than saving the .toe file and does not block the TD UI.
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.
- 5d ago First seen · 16 lines · 11 tokens per session scan A 78a73c0e9bb8
td-snapshot is a command published in the GitHub repository dreamrec/TDPilot (11 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 147 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.
Other commands, from other repositories
validate
Pre-handoff validation checklist. Run this before declaring a task complete.
run-tests
Load the /run-tests skill, then run the full Embody test suite via MCP.
explore-network
Explore the current TouchDesigner network and report its structure.
status
Perform a quick health check of the Embody project.
checklist
Generate a custom checklist for the current feature based on user requirements.
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.