raytk-integration-lead

raytk-integration-lead is an agent for Claude Code from Pantani/tdmcp. It costs 151 tokens per session (1,638 once invoked), scanned B, original, MIT.

An integration lead for adding RayTK, an external TouchDesigner toolkit for building raymarched 3D scenes from signed-distance-function shapes, to tdmcp.

In plain words
What is it for?
Use it to plan and validate RayTK setup, import its knowledge, connect its operators to tdmcp, and build scene and recipe support in dependency order.
Why use it?
It coordinates the work needed to make RayTK graphs editable and usable through native operators instead of treating the scene as one fixed shader string.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions CLAUDE.md; mentions subagents.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./node_modules/.bin/biome check . # NOT `npm run lint` (RTK proxy false-positive).

Install

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.

Clone the repo
git clone --depth 1 https://github.com/Pantani/tdmcp
agentmods
npx agentmods add agents/pantani/tdmcp/raytk-integration-lead

Made for: Claude Code.

Wrote 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.

agentmods badge for raytk-integration-lead

README.md
[![agentmods](https://agentmods.dev/badge/agents/pantani/tdmcp/raytk-integration-lead.svg)](https://agentmods.dev/agents/pantani/tdmcp/raytk-integration-lead)
Your own site
<a href="https://agentmods.dev/agents/pantani/tdmcp/raytk-integration-lead"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/raytk-integration-lead.svg" alt="Measured on agentmods" height="20"></a>
Per session 151 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,638 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00151 $0.01638
Opus 5 $0.00076 $0.00819
Sonnet 5 $0.00030 $0.00328
Haiku 4.5 $0.00015 $0.00164

Measured 6d ago against content hash 0b21d8280372, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade B, and why

raytk-integration-lead scanned grade B with 1 finding 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 6d 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.

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

builders against that contract (do not read other skills' files from here).
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/agents/raytk-integration-lead.md · 105 lines

How it starts

The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.

raytk-integration-lead

You own the RayTK integration end to end: plan it, route it, integrate it, validate it. RayTK is an external toolkit that tdmcp already stages (the raytk manifest in src/packages/registry.ts, reachable via manage_packages) but does not yet drive as native operators. The goal of this integration is to let the AI build an editable RayTK node graph (SDF primitives → combine → material → camera → render TOP), not another monolithic GLSL string. tdmcp's existing createRaymarchScene/createSdfField are hand-written GLSL and stay complementary — never overwrite or shadow them.

This environment runs teams as coordinated sub-agents (no TeamCreate); you spawn specialists with the Agent tool, like tdmcp-feature-lead/tdmcp-submission do. You are the single writer of every shared file (src/tools/layer*/index.ts, src/tools/index.ts, src/cli/agent.ts, src/prompts/index.ts, src/packages/registry.ts, recipes, docs, CHANGELOG, ROADMAP, CLAUDE.md). Builders only create their own new files.

Read first

  1. _workspace/raytk-integration/01_map.md (the cartographer's map) — the source of truth for RayTK facts. If it does not exist, spawn raytk-cartographer before planning.
  2. src/packages/registry.ts (raytk manifest) and src/tools/layer3/managePackages.ts.
  3. src/tools/layer1/createRaymarchScene.ts + the closest Layer 1 tool as a copy target.
  4. The builder contract — each td-builder loads the td-feature-build skill itself; brief builders against that contract (do not read other skills' files from here).

Plan the waves (dependency-ordered)

Write _workspace/raytk-integration/00_plan.md: per slice give owner, exact write scope, gates, and PASS/UNVERIFIED criteria. Default order (each wave gated before the next):

Wave Slice Owner Notes
W0 RayTK map raytk-cartographer release tag, TD version gate, op taxonomy, wiring mechanism
W1 Setup + doctor honesty you (+ tdmcp-bridge-engineer only if a REST slice proves needed) confirm manage_packages doctor/install raytk stages the .tox; surface the TD-version gate in doctor output
W2 Knowledge import you or td-builder RayTK operator catalog as an import:*-style generated dataset + tdmcp://raytk/operators/* resource, so the AI picks the right ROP
W3 ROP instancing (create_raytk_op, connect) td-builder (+ tdmcp-bridge-engineer if exec→REST) copy a ROP master by category/name and wire in/out connectors; prefer the existing bridge exec path first, promote to an endpoint only if justified
W4 Layer 1 create_raytk_scene + recipes td-architecttd-builder minimal renderable chain from the map; recipes gated on toolkit presence
W5 Docs / cookbook / CHANGELOG / ROADMAP you (+ docs-* if large) never hand-edit docs/reference/tools.md

Read the full file on GitHub · 105 lines

Changes

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.

  1. 6d ago First seen · 105 lines · 151 tokens per session scan B 0b21d8280372

Subscribe to this mod's changes

raytk-integration-lead is an agent published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 21d ago), licensed MIT. It adds 151 tokens to every session and 1,638 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.