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/lucasmaher-hash/touch-designer-mcpnpx agentmods add agents/lucasmaher-hash/touch-designer-mcp/raytk-integration-leadWrote 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/lucasmaher-hash/touch-designer-mcp/raytk-integration-lead)<a href="https://agentmods.dev/agents/lucasmaher-hash/touch-designer-mcp/raytk-integration-lead"><img src="https://agentmods.dev/badge/agents/lucasmaher-hash/touch-designer-mcp/raytk-integration-lead/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/lucasmaher-hash/touch-designer-mcp/raytk-integration-lead"><img src="https://agentmods.dev/badge/agents/lucasmaher-hash/touch-designer-mcp/raytk-integration-lead.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.00151 | $0.01638 |
| Opus 5 | $0.00076 | $0.00819 |
| Sonnet 5 | $0.00030 | $0.00328 |
| Haiku 4.5 | $0.00015 | $0.00164 |
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 10d 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). This is a copy
100% identical to raytk-integration-lead — 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 — 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
_workspace/raytk-integration/01_map.md(the cartographer's map) — the source of truth for RayTK facts. If it does not exist, spawnraytk-cartographerbefore planning.src/packages/registry.ts(raytkmanifest) andsrc/tools/layer3/managePackages.ts.src/tools/layer1/createRaymarchScene.ts+ the closest Layer 1 tool as a copy target.- The builder contract — each
td-builderloads thetd-feature-buildskill 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-architect → td-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 |
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.
- 10d ago First seen · 105 lines · 151 tokens per session scan B 0b21d8280372
raytk-integration-lead is an agent published in the GitHub repository lucasmaher-hash/touch-designer-mcp (0 stars, last pushed 1mo 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). It is 100% identical to raytk-integration-lead, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
game-engine-architect
Specialized game engine architect with expertise in engine architecture, rendering systems, and game physics. Use when designing game engines, implementing core engine systems, or optimizing engine performance.
game-tools-engineer
Use when building game development tools, editors, asset pipelines, build systems, and workflow automation. Expert in tooling that multiplies team productivity.