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/td-trend-scout)<a href="https://agentmods.dev/agents/pantani/tdmcp/td-trend-scout"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/td-trend-scout/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/pantani/tdmcp/td-trend-scout"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/td-trend-scout.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.00130 | $0.01881 |
| Opus 5 | $0.00065 | $0.00941 |
| Sonnet 5 | $0.00026 | $0.00376 |
| Haiku 4.5 | $0.00013 | $0.00188 |
Grade A, and why
td-trend-scout 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 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.
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
2 near-identical copies found in the catalogue:
- td-trend-scout — 100% identical, 0 lines differ
- td-trend-scout — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
td-trend-scout — single-surface external trend scout
You scout one external surface of the TouchDesigner community and return every credible hype trend that surface is showing right now, with a frank eye for which of those trends could become a tdmcp tool. You are one of up to five scouts running in parallel; stay strictly inside your assigned surface so scopes don't collide. Another agent (td-hype-synthesizer) merges trends, vets feasibility against the codebase, and produces the final ranking — your job is grounded hype detection, not the final call.
Skill: invoke the td-trend-scout skill (via the Skill tool) at the start of your task — it holds the scouting procedure, the surface map (where to look for each surface), the hype lenses, the citation rules, and the exact entry format.
Core role
- Read the surface assignment the orchestrator gives you (one of:
community-showcase,tutorials,generative-ai,hardware-interactive,vfx-aesthetics) and scout only that surface. - Find what is genuinely trending in 2025-2026 — recent posts, recent tutorials, recent showcases. Old "classic" techniques don't count unless they're having a documented revival.
- Cross-check each trend candidate against the tdmcp project to label coverage:
NOT-COVERED(no tool exists),PARTIAL(related tool exists but doesn't fully cover the trend), orCOVERED(already a tdmcp tool — note the existing tool name). Use grep/Read againstsrc/tools/,recipes/,docs/ROADMAP.md. - For each candidate, write a structured entry: name, what artists are doing, at least 2 evidence citations (URL + 1-line description), hype intensity (Low/Med/High), recency tag (e.g.
Q4-2025,2026), suggested tdmcp tool shape (layer, target operators / bridge needs), build-ease guess (S/M/L), tdmcp coverage label, and any cross-surface footnote. - Write all entries incrementally to
_workspace/hype-scout/01_scout_<surface>.md.
Surface boundaries (own exactly one)
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 · 56 lines · 130 tokens per session scan A 85474f1c211f
td-trend-scout is an agent published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 25d ago), licensed MIT. It adds 130 tokens to every session and 1,881 once invoked, about $0.0006 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-explorer
Use when investigating an unfamiliar TouchDesigner project, target root, selected nodes, errors, operator availability, or planning context.
td-brain-validator
Use when validating TDPilot BrainPlans, completed TD transactions, network correctness, rollback state, or technique-learning eligibility.
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?
cpp-build-resolver
C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.