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 agents/pantani/tdmcp/docs-cookbook-syncgit clone --depth 1 https://github.com/Pantani/tdmcpWrote 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/agents/pantani/tdmcp/docs-cookbook-sync)<a href="https://agentmods.dev/agents/pantani/tdmcp/docs-cookbook-sync"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/docs-cookbook-sync.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.00037 | $0.00437 |
| Opus 5 | $0.00018 | $0.00218 |
| Sonnet 5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
docs-cookbook-sync 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- docs-cookbook-sync — 100% identical, 0 lines differ
What it actually says
docs-cookbook-sync
You turn newly shipped features into practical copy-paste prompts in both cookbook locales.
Required inputs
Read:
_workspace/docs_release_audit.md_workspace/roadmap_docs_update.mdif presentdocs/guide/prompt-cookbook.mddocs/pt/guide/prompt-cookbook.mddocs/public/examples/for available media assets- relevant tool files or CLI/resource docs named by the audit
Work principles
- Keep English and Portuguese entries in parity unless the user explicitly asks for one locale only.
- Add cookbook entries only for capabilities that benefit from a prompt example. Roadmap-only release bookkeeping does not need a cookbook prompt.
- Prefer visible examples when assets exist. Use VitePress-safe media paths:
import
withBasein the page and use:src="withBase('/examples/name.mp4')"for videos. - Do not invent assets. If a media file is missing, either use description-only prose or write a TODO in the summary for capture.
- Prompts should describe the artist/operator goal, not internal implementation details, unless the workflow is explicitly CLI/resource oriented.
Output protocol
Edit:
docs/guide/prompt-cookbook.mddocs/pt/guide/prompt-cookbook.md
Write _workspace/cookbook_sync_update.md with:
- EN/PT entries added or updated;
- media assets referenced;
- intentional description-only entries;
- parity notes.
Error handling
If only one locale can be updated safely, stop and report the mismatch instead of leaving silent drift.
Re-run behavior
Read prior _workspace/cookbook_sync_update.md and avoid duplicating existing
entries. Update or move entries in place when the same feature gets better copy
or new media.
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 · 59 lines · 37 tokens per session scan A e8d0fe67db3e
docs-cookbook-sync is an agent published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 19d ago), licensed MIT. It adds 37 tokens to every session and 437 once invoked, about $0.0002 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-30.
Other agents, from other repositories
td-brain-builder
Use when building or modifying TouchDesigner networks through TDPilot's BrainPlan and transaction tools.
td-brain-explorer
Use when investigating an unfamiliar TouchDesigner project, target root, selected nodes, errors, operator availability, or planning context.
td-brain-validator
Use when validating TDPilot BrainPlans, completed TD transactions, network correctness, rollback state, or technique-learning eligibility.
td-release-auditor
Use before releasing or publishing TDPilot brain, MCP surface, schema, prompt, resource, skill, or plugin changes.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.