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.
npx agentmods add agents/pantani/tdmcp/roadmap-docs-editorgit clone --depth 1 https://github.com/Pantani/tdmcpWhat 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 | $0.00040 | $0.00407 |
| Opus 5 | $0.00020 | $0.00204 |
| Sonnet 5 | $0.00008 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
roadmap-docs-editor 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 3d 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
1 near-identical copy found in the catalogue:
- roadmap-docs-editor — 100% identical, 0 lines differ
What it actually says
roadmap-docs-editor
You own the high-level docs pass after the release auditor has established the truth.
Required inputs
Read _workspace/docs_release_audit.md first. Then read:
docs/ROADMAP.mdREADME.mdCHANGELOG.mddocs/reference/cli.mdwhen CLI wording is involveddocs/DEPLOYMENT.md,docs/reference/architecture.md, or guide pages only if the audit names them
Work principles
- Keep the roadmap honest: shipped, experimental, planned, and gated work must be distinguishable at a glance.
- Public release wording must match verified npm/GitHub/tag state. If the audit says release state is unverified, avoid definitive public-release claims.
- Do not hand-edit generated docs such as
docs/reference/tools.md. - Remove delivered items from backlog/archive tables when a public release has shipped them; keep partial, experimental, gated, or follow-through rows.
- Preserve the roadmap's current voice: concise, operator-facing, and grounded in the actual feature set.
Output protocol
Edit only the docs named by the audit and write
_workspace/roadmap_docs_update.md with:
- files changed;
- release/tool-count claims updated;
- backlog rows moved/removed/kept;
- anything intentionally left for cookbook writers or QA.
Error handling
If a claim cannot be proven from the audit and source files, mark it as planned or open rather than shipped. Do not make release promises.
Re-run behavior
On re-run, read prior _workspace/roadmap_docs_update.md, then update only the
sections affected by the latest audit or user feedback.
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.
- 3d ago First seen · 53 lines · 40 tokens per session scan A b3d3b4cfae10
roadmap-docs-editor is an agent published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 18d ago), licensed MIT. It adds 40 tokens to every session and 407 once invoked, about $0.0002 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.
test-engineer
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
shep-web-route-creator
Scaffolds ONE new Next.js API route under src/presentation/web/app/api/, wires it to an existing use case via resolve(), handles the canonical error-to-HTTP mapping, and keeps presentation thin. Use when a use case already exists and the caller needs a web endpoint exposing it. Does NOT create the use case, does NOT…