Borrowing it
Nothing to install: this file belongs to bottobot/touchdesigner-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bottobot/touchdesigner-mcp-server/main/.claude/agents/validate-experimental.mdgit clone --depth 1 https://github.com/bottobot/touchdesigner-mcp-serverWrote 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/bottobot/touchdesigner-mcp-server/validate-experimental)<a href="https://agentmods.dev/agents/bottobot/touchdesigner-mcp-server/validate-experimental"><img src="https://agentmods.dev/badge/agents/bottobot/touchdesigner-mcp-server/validate-experimental/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/bottobot/touchdesigner-mcp-server/validate-experimental"><img src="https://agentmods.dev/badge/agents/bottobot/touchdesigner-mcp-server/validate-experimental.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.00008 | $0.00323 |
| Opus 5.5 | $0.00003 | $0.00129 |
| Sonnet 5.5 | $0.00002 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
validate-experimental 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 1mo 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.
What it actually says
You are validating the experimental features implementation in the TouchDesigner MCP Server.
Project location: /home/robert/Documents/TD-MCP/touchdesigner-mcp-server
Tasks:
- Run: node --check tools/get_experimental_techniques.js
- Run: node --check tools/search_experimental.js
- Run: node --check tools/get_glsl_pattern.js
- Run: node --check index.js
- Verify all /wiki/data/experimental/*.json are valid JSON: node -e "const fs=require('fs'); ['glsl','gpu-compute','machine-learning','generative-systems','audio-visual','networking','python-advanced'].forEach(c => { try { JSON.parse(fs.readFileSync('wiki/data/experimental/'+c+'.json','utf8')); console.log(c+': valid'); } catch(e) { console.error(c+': INVALID - '+e.message); } })"
- Verify new operator files in /wiki/data/processed/ (feedback_top, noise_top, etc.) are valid JSON
- Check index.js registers 'get_experimental_techniques', 'search_experimental', 'get_glsl_pattern'
- Verify at least 3 experimental technique files have codeExample fields with actual code
Fix ANY issues found before completing. If a file is missing, create a minimal valid version.
Report: All experimental files created/validated, techniques count per category, fixes applied.
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.
- 1mo ago First seen · 24 lines · 8 tokens per session scan A 73d7c50a88c7
validate-experimental is an agent published in the GitHub repository bottobot/touchdesigner-mcp-server (80 stars, last pushed 28d ago), licensed MIT. It adds 8 tokens to every session and 323 once invoked, about $0.0000 per session on Opus 5.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
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
codebase-explorer
Explores a codebase to discover implementation details for a specific feature or system. Finds entry points, core logic, data models, configuration, tests, and feature-type-specific artifacts. Use when thorough, multi-angle codebase discovery is needed for documentation or understanding. Does not research options or…
tea
Master Test Architect and Quality Advisor.
regression-sentinel
Watch evaluation metrics over time for trends and regressions. Unlike verification-judge (validates single work items against specs), this agent watches metric trends across sessions and flags gradual degradation before it becomes critical. Use after session-end metrics collection or as a daily rollup.
dependency-verifier
Verify that external dependencies, APIs, specs, and tools actually behave as documented. Use when you need to validate assumptions about external systems, check if a spec is actually implemented, or investigate ecosystem adoption of a feature. This agent tests against real-world implementations, not just documentation.
tdd-developer
MANDATORY AGENT when TDD mode is active (.claude/.tdd-mode-active file exists). You MUST spawn this agent for ANY coding request when TDD mode is active, including: New features (frontend, backend, API, UI) Bug fixes UI changes (styling, components, layouts) API changes Configuration changes Refactoring ANY file…