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 skills add lucasmaher-hash/touch-designer-mcp --skill tdmcp-cookbook-examplesgit clone --depth 1 https://github.com/lucasmaher-hash/touch-designer-mcpWrote 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/skills/lucasmaher-hash/touch-designer-mcp/tdmcp-cookbook-examples)<a href="https://agentmods.dev/skills/lucasmaher-hash/touch-designer-mcp/tdmcp-cookbook-examples"><img src="https://agentmods.dev/badge/skills/lucasmaher-hash/touch-designer-mcp/tdmcp-cookbook-examples/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/skills/lucasmaher-hash/touch-designer-mcp/tdmcp-cookbook-examples"><img src="https://agentmods.dev/badge/skills/lucasmaher-hash/touch-designer-mcp/tdmcp-cookbook-examples.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.00094 | $0.00935 |
| Opus 5 | $0.00047 | $0.00467 |
| Sonnet 5 | $0.00019 | $0.00187 |
| Haiku 4.5 | $0.00009 | $0.00093 |
Grade A, and why
tdmcp-cookbook-examples 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 12d 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.
This is a copy
100% identical to tdmcp-cookbook-examples — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tdmcp-cookbook-examples
Adds new, visually impressive examples to docs/guide/prompt-cookbook.md (EN)
and docs/pt/guide/prompt-cookbook.md (PT).
Execution mode: sub-agents (sequential curation → parallel EN+PT writing).
Phase 0: context check
Before doing anything, check:
- Does
_workspace/cookbook_candidates.mdalready exist?- YES + the user asked to "re-run" or "update" → skip curation, reuse candidates.
- YES + user gave new direction → rename old to
_workspace/cookbook_candidates_prev.md, re-curate. - NO → proceed with full Phase 1.
Phase 1: curate
Spawn the cookbook-curator agent with this prompt:
Read the task description in .Codex/agents/cookbook-curator.md and execute it.
Survey src/tools/layer1/index.ts, src/tools/layer2/index.ts, recipes/*.json,
docs/ROADMAP.md, CHANGELOG.md, and docs/guide/prompt-cookbook.md.
Produce _workspace/cookbook_candidates.md with 15-20 new cookbook candidates.
Wait for it to finish before continuing.
Phase 2: write (parallel)
Once _workspace/cookbook_candidates.md exists, spawn two writer agents in parallel:
EN writer:
Read .Codex/agents/cookbook-writer.md for your role and format rules.
Language: English.
Target file: docs/guide/prompt-cookbook.md
Candidates: _workspace/cookbook_candidates.md
Add all candidates marked for EN to the target file, following the exact format.
Write a summary to _workspace/cookbook_write_en.md when done.
PT writer:
Read .Codex/agents/cookbook-writer.md for your role and format rules.
Language: Brazilian Portuguese.
Target file: docs/pt/guide/prompt-cookbook.md
Candidates: _workspace/cookbook_candidates.md
Add all candidates to the target file, translating from the EN prompts in the
candidates file. Match the existing PT file's voice and format.
Write a summary to _workspace/cookbook_write_pt.md when done.
Phase 3: QA
After both writers finish, do a quick consistency check:
- Count entries in EN file vs PT file — the number of new entries should match.
- Spot-check 3 random new entries: verify the tool name in the result-description
exists in
src/tools/layer1/index.tsorsrc/tools/layer2/index.ts. - Check no media reference (
/examples/SLUG.mp4or.png) points to a file that already exists indocs/public/examples/under a conflicting name. - Verify both files still start with valid YAML frontmatter.
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.
- 12d ago First seen · 96 lines · 94 tokens per session scan A 2338f8b74674
tdmcp-cookbook-examples is a skill published in the GitHub repository lucasmaher-hash/touch-designer-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 94 tokens to every session and 935 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to tdmcp-cookbook-examples, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…