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/lucasmaher-hash/touch-designer-mcpWrote 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/roadmap-docs-editor)<a href="https://agentmods.dev/agents/lucasmaher-hash/touch-designer-mcp/roadmap-docs-editor"><img src="https://agentmods.dev/badge/agents/lucasmaher-hash/touch-designer-mcp/roadmap-docs-editor.svg" alt="Measured on agentmods" 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.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 6d 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.
This is a copy
100% identical to roadmap-docs-editor — 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.
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.
- 6d ago First seen · 53 lines · 40 tokens per session scan A b3d3b4cfae10
roadmap-docs-editor is an agent published in the GitHub repository lucasmaher-hash/touch-designer-mcp (0 stars, last pushed 1mo 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. It is 100% identical to roadmap-docs-editor, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.