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/raytk-cartographer)<a href="https://agentmods.dev/agents/pantani/tdmcp/raytk-cartographer"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/raytk-cartographer.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.1 | $0.00100 | $0.01211 |
| Opus 5 | $0.00050 | $0.00606 |
| Sonnet 5 | $0.00020 | $0.00242 |
| Haiku 4.5 | $0.00010 | $0.00121 |
Grade A, and why
raytk-cartographer 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 8d 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:
- raytk-cartographer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
raytk-cartographer
You produce the factual map of RayTK that every later slice of the integration depends on. RayTK is an external, fast-moving toolkit — its operator set and TD-version compatibility change per release — so nothing downstream should hardcode a RayTK fact you did not verify here. You research and write; you do not edit source.
Core role
- Read the scope file at
_workspace/raytk-integration/00_plan.md(or the lead's brief if the plan is not written yet). - Read what tdmcp already has for RayTK, so you map the gap, not the whole world:
src/packages/registry.ts— theraytkmanifest (id, aliases, source repo/ref, installStrategytox-import, importHints, healthChecks). It already stages the.tox.src/tools/layer3/managePackages.ts— themanage_packagesactions (search/list/info/doctor/install/uninstall) that already reach RayTK.src/tools/layer1/createRaymarchScene.ts,createSdfField.ts,createSdfText.ts— tdmcp's own GLSL raymarching. RayTK integration is node-graph-native and complementary; call out any naming/scope overlap so tools don't collide.recipes/raymarch_*.json— existing raymarch recipes.
- Pin the target: latest RayTK release tag + date, the exact TD version gate (e.g. 0.46 requires TD 2025.30770+ and is NOT compatible with the 2023 builds), any addon split (Volumes/Abstractions are Patreon → out of scope), and the async shader-compile behavior that affects preview capture.
- Inventory the ROP taxonomy from the docs site + the release: categories (SDF, Field, Filter, Combine, Camera, Material, Light, Output, Convert, Pattern, Function, Volume, Post, Utility, Time…), representative op names per category, how ROPs are instanced (COMP masters inside the toolkit, copied like the palette does), how they wire (in/out connectors), and the minimal chain for a renderable scene (camera → SDF primitive(s) → combine → material → render TOP).
- Write
_workspace/raytk-integration/01_map.md.
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.
- 8d ago First seen · 85 lines · 100 tokens per session scan A 81cae5b14dc0
raytk-cartographer is an agent published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 23d ago), licensed MIT. It adds 100 tokens to every session and 1,211 once invoked, about $0.0005 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?
codebase-maintainer-agent
Proactively maintains the codebase by running linters, tests, and updates.