Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/hybridlabor-api/bdb-dev-optimized-agent-skillsnpx agentmods add skills/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-tool-builderWrote 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/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-tool-builder)<a href="https://agentmods.dev/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-tool-builder"><img src="https://agentmods.dev/badge/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-tool-builder/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/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-tool-builder"><img src="https://agentmods.dev/badge/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-tool-builder.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.00144 | $0.03085 |
| Opus 5 | $0.00072 | $0.01543 |
| Sonnet 5 | $0.00029 | $0.00617 |
| Haiku 4.5 | $0.00014 | $0.00309 |
Grade A, and why
tdmcp-tool-builder 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.
This is a copy
100% identical to tdmcp-tool-builder — 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tdmcp-tool-builder
You build one new tdmcp tool, end to end, matching the repo so closely a reviewer cannot tell which files are new. tdmcp is a TouchDesigner MCP server: a Node/TS server (this repo) drives a Python bridge running inside TouchDesigner. A "tool" is a TS handler that the AI can call; most tools do their work by sending one Python script to the bridge and parsing a JSON report back.
The canonical template is src/tools/layer2/manageComponent.ts. Read it
first, every time. Copy its shape exactly. The rules below explain why each
piece exists so you make the right call on edge cases.
The contract: one file, two exports (+ schema)
Every tool file exports three things and nothing surprising:
export const xSchema = z.object({ … })— the Zod input schema. Each field gets a.describe()written for an AI caller (say what it does and the units).export async function xImpl(ctx: ToolContext, args): Promise<CallToolResult>— the pure, testable handler. It takes the injectedToolContext({ client, knowledge, recipes, logger, vault?, allowRawPython }) and the validated args. All TD work goes throughctx.client. Unit tests call this directly with a mocked client — so it must never read globals or env directly.export const registerX: ToolRegistrar = (server, ctx) => server.registerTool( name, { title, description, inputSchema: xSchema.shape, annotations }, (args) => xImpl(ctx, args)).
Types come from ../types.js (ToolContext, ToolRegistrar). The name is
snake_case (add_custom_parameters); the file is camelCase
(addCustomParameters.ts); the registrar is registerAddCustomParameters.
annotations describe side effects for the client UI. Mutating builders use
{ readOnlyHint: false, destructiveHint: false, openWorldHint: true }. Pure read
tools use { readOnlyHint: true, openWorldHint: true }. A tool that can wipe data
sets destructiveHint: true.
Read tools: prefer structuredResult + outputSchema
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 · 230 lines · 144 tokens per session scan A 1f34a1c9e395
tdmcp-tool-builder is a skill published in the GitHub repository hybridlabor-api/bdb-dev-optimized-agent-skills (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 144 tokens to every session and 3,085 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to tdmcp-tool-builder, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.
context-engineering
Dynamic context injection, mode switching (dev/review/research), selective loading, and strategic compaction for token optimization.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
multi-app-orchestration
Orchestrate workflows across multiple applications and APIs — inter-app coordination, data handoff, and multi-system task completion.
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
bento
Modular grid layout with card-like blocks, clear hierarchy, soft spacing, and subtle visual contrast for organized, scannable interfaces.