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-checkgit 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-check)<a href="https://agentmods.dev/commands/dreamrec/tdpilot/td-check"><img src="https://agentmods.dev/badge/commands/dreamrec/tdpilot/td-check.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.00010 | $0.00140 |
| Opus 5 | $0.00005 | $0.00070 |
| Sonnet 5 | $0.00002 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
td-check 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 4d 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 the td_ MCP tools to run a full health check on the current TouchDesigner
project:
- Call
td_get_infoto confirm the session is alive and grab project name + TD build. - Call
td_get_errorson the project root to surface any cooking or connection errors. - Call
td_get_capabilitiesto confirm feature availability (vision, memory, safety). - Call
td_describe_surfaceto report live tool count and server version.
Summarize findings concisely. Flag errors/warnings first, then capability deltas or version drift.
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.
- 4d ago First seen · 15 lines · 10 tokens per session scan A caf621b50361
td-check is a command published in the GitHub repository dreamrec/TDPilot (11 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 140 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.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.