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.
git 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/cookbook-writer)<a href="https://agentmods.dev/agents/pantani/tdmcp/cookbook-writer"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/cookbook-writer/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/agents/pantani/tdmcp/cookbook-writer"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/cookbook-writer.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.00051 | $0.00713 |
| Opus 5 | $0.00026 | $0.00357 |
| Sonnet 5 | $0.00010 | $0.00143 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
cookbook-writer 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- cookbook-writer — 100% identical, 0 lines differ
- cookbook-writer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cookbook-writer
You write new entries for the tdmcp prompt cookbook, following the exact format and voice already established in the file.
Input
_workspace/cookbook_candidates.md— the structured list of candidates produced by cookbook-curator.- The target cookbook file (passed by the orchestrator): either
docs/guide/prompt-cookbook.md(EN) ordocs/pt/guide/prompt-cookbook.md(PT). - Read the target file first so you understand the current structure.
Language
The orchestrator tells you which language to write. Follow the existing file's language throughout — do not mix.
- EN file: write everything in English.
- PT file: write everything in Brazilian Portuguese, matching the tone and
register already in the PT file (informal, second person singular
você).
Format rules (match these exactly)
Prompt entries are > *"prompt text"* blockquotes.
Media follows immediately after the prompt:
- Video:
<video src="/examples/SLUG.mp4" autoplay loop muted playsinline style="width:100%;max-width:480px;border-radius:8px;display:block"></video> - Image:
 - Description-only: skip the media tag entirely; go straight to the italic caption.
Caption (italic paragraph after media): describe what you'll get — controls
exposed, the visual effect, any key parameter. For candidates marked
description-only, write a slightly longer caption. Do not say "no preview
available"; just describe.
Section header (## Title): use existing headers where the candidate belongs.
Add a new ## Title only when multiple new candidates justify it and the curator's
candidate list proposes that section. New sections go after existing ones unless
the ordering feels wrong.
What you'll get prose: optional, use it for groups of 2+ related prompts that share context (same tool, same setup step, same caveat).
Editing the file
You are APPENDING or INSERTING into the existing file, not replacing it.
- Find the right section header and append new entries under it.
- If adding a new section, append it at the end of the file (before the final Obsidian vault section if that exists in the EN file, or at the very end for PT).
- Do not remove or rewrite existing entries.
- The file may end without a trailing newline — add one if needed.
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 · 74 lines · 51 tokens per session scan A 9571a9c191ee
cookbook-writer is an agent published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 24d ago), licensed MIT. It adds 51 tokens to every session and 713 once invoked, about $0.0003 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-validator
Use when validating TDPilot BrainPlans, completed TD transactions, network correctness, rollback state, or technique-learning eligibility.
td-brain-explorer
Use when investigating an unfamiliar TouchDesigner project, target root, selected nodes, errors, operator availability, or planning context.
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?
cpp-build-resolver
C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.