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 skills add lucasmaher-hash/touch-designer-mcp --skill tdmcp-roadmap-campaigngit 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/skills/lucasmaher-hash/touch-designer-mcp/tdmcp-roadmap-campaign)<a href="https://agentmods.dev/skills/lucasmaher-hash/touch-designer-mcp/tdmcp-roadmap-campaign"><img src="https://agentmods.dev/badge/skills/lucasmaher-hash/touch-designer-mcp/tdmcp-roadmap-campaign/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/skills/lucasmaher-hash/touch-designer-mcp/tdmcp-roadmap-campaign"><img src="https://agentmods.dev/badge/skills/lucasmaher-hash/touch-designer-mcp/tdmcp-roadmap-campaign.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.00279 | $0.02073 |
| Opus 5 | $0.00139 | $0.01037 |
| Sonnet 5 | $0.00056 | $0.00415 |
| Haiku 4.5 | $0.00028 | $0.00207 |
Grade A, and why
tdmcp-roadmap-campaign 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 9d 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 tdmcp-roadmap-campaign — 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.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tdmcp Roadmap-to-1.0 Campaign
Drives _workspace/campaign_roadmap_v1/ROADMAP_1.0_BACKLOG.md to completion,
gated by _workspace/campaign_roadmap_v1/ledger.json (idempotent, resumable,
merge-safe). This is orchestration only — it never writes product code
itself; it routes each ledger item to the existing specialist sub-harness and
records the outcome back into the ledger.
Why this exists (vs tdmcp-backlog-campaign)
tdmcp-backlog-campaign drives a tool-shaped backlog through one pipeline
(design→build→integrate→QA→release). The road to 1.0 is not uniform: it mixes
new tools (M4), a policy-bounded mixer slice (M5), a coverage CI gate (G2), a
bridge exec→REST sweep (G4), docs/governance (G1/G5/G6 prep), and live-validated
recipes (G3). Each needs a different specialist. This skill is the thin router
that sequences them and keeps one ledger of truth.
Confirmed campaign policy (2026-06-21)
- Release: commit + push, NO tag/bump. Everything lands in CHANGELOG
[Unreleased]. Cutting the version is a manual user step — never tag autonomously ([[no-premature-release-tag]]). - Blocked items (GPU/CUDA, live-TD, external service): build offline +
quarantine. Implement, pass the offline gates, set
liveto the rightUNVERIFIED-pending-*marker, keep going. Quarantine never blocks the campaign. - Checkpoint: after Wave 1 only, then autonomous to the end. On repeat failure: retry once → quarantine-and-continue (note it in the wave report).
Routing table (ledger route → sub-harness)
route |
Sub-harness | Agents |
|---|---|---|
docs |
tdmcp-docs-roadmap-update |
roadmap-docs-editor, docs-cookbook-sync, docs-roadmap-qa |
tools |
tdmcp-feature-lead |
tdmcp-tool-builder ×N + single-writer integration |
mixer |
tdmcp-pipeline |
mixer-scene-contract-architect, soundcraft-ui24r-adapter-architect, mixer-policy-safety-qa |
coverage |
tdmcp-test-coverage |
tdmcp-coverage-writer, tdmcp-coverage-qa |
bridge |
tdmcp-bridge-endpoint |
tdmcp-bridge-engineer (sequential — bridge slices share files) |
recipes |
tdmcp-pipeline |
td-architect, td-builder, td-qa (needs live TD) |
submission |
tdmcp-submission |
submission-architect, submission-qa |
| planning | — | tdmcp-backlog-planner (wave computation + ledger transitions) |
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.
- 9d ago First seen · 144 lines · 279 tokens per session scan A bef1dc262463
tdmcp-roadmap-campaign is a skill published in the GitHub repository lucasmaher-hash/touch-designer-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 279 tokens to every session and 2,073 once invoked, about $0.0014 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to tdmcp-roadmap-campaign, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.