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/final-validate.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/final-validate)<a href="https://agentmods.dev/agents/bottobot/touchdesigner-mcp-server/final-validate"><img src="https://agentmods.dev/badge/agents/bottobot/touchdesigner-mcp-server/final-validate/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/final-validate"><img src="https://agentmods.dev/badge/agents/bottobot/touchdesigner-mcp-server/final-validate.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.00011 | $0.00356 |
| Opus 5.5 | $0.00004 | $0.00142 |
| Sonnet 5.5 | $0.00002 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
final-validate 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 performing final validation of core tool enhancements and documentation for the TouchDesigner MCP Server.
Project location: /home/robert/Documents/TD-MCP/touchdesigner-mcp-server
Tasks:
- Run: node --check tools/get_operator_connections.js
- Run: node --check tools/get_network_template.js
- Run: node --check tools/search_operators.js
- Run: node --check tools/suggest_workflow.js
- Run: node --check index.js
- Validate search index: node -e "const d=JSON.parse(require('fs').readFileSync('wiki/data/search-index/search-index.json','utf8')); console.log('Search index entries:', Array.isArray(d) ? d.length : Object.keys(d).length);"
- Count total operators in /wiki/data/processed/: ls -la wiki/data/processed/ | wc -l
- Verify README.md is at least 2000 characters (indicates substantial content)
- Verify CHANGELOG.md has a 2.0.0 entry
- Verify index.js registers: get_operator_connections, get_network_template
Fix ANY issues found before completing.
Provide a COMPREHENSIVE FINAL SUMMARY of everything accomplished across ALL parallel streams:
- Version system: files created, tools added, operators versioned
- Experimental features: categories created, techniques documented, tools added
- Core enhancements: operators added, search improved, new tools
- Documentation: files updated
- Total new/modified files count
- Total registered MCP tools (before vs after)
- Any remaining known issues or recommendations
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 · 32 lines · 11 tokens per session scan A e2f63bcc2c9b
final-validate is an agent published in the GitHub repository bottobot/touchdesigner-mcp-server (80 stars, last pushed 28d ago), licensed MIT. It adds 11 tokens to every session and 356 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…