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-pipelinegit 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-pipeline)<a href="https://agentmods.dev/skills/lucasmaher-hash/touch-designer-mcp/tdmcp-pipeline"><img src="https://agentmods.dev/badge/skills/lucasmaher-hash/touch-designer-mcp/tdmcp-pipeline/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-pipeline"><img src="https://agentmods.dev/badge/skills/lucasmaher-hash/touch-designer-mcp/tdmcp-pipeline.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.00128 | $0.02193 |
| Opus 5 | $0.00064 | $0.01097 |
| Sonnet 5 | $0.00026 | $0.00439 |
| Haiku 4.5 | $0.00013 | $0.00219 |
Grade A, and why
tdmcp-pipeline 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 12d 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-pipeline — 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tdmcp-pipeline — feature delivery orchestrator
Coordinate the five tdmcp specialists to take feature ideas from spec to a pushed release, following the project's proven workflow: parallel isolated builders + a single-writer integrator + live-validated QA + an autonomous release.
Execution mode: hybrid
| Stage | Mode | Why |
|---|---|---|
| Design | sub-agent (fan-out if many features) | the architect is an isolated one-shot producer; specs land in _workspace/ |
| Build | sub-agent (fan-out, parallel) | builders are fully isolated by design (new files only, no inter-comms) — the textbook sub-agent case |
| Integrate → QA → Release | agent team | producer↔reviewer feedback loops (QA ↔ builder-fixer/integrator) and the release gate need live messaging |
Why this split: builders must NOT touch shared files so they can run concurrently; that isolation removes any need for build-time team comms. The integrate/QA/release trio, by contrast, lives on a tight fix-and-re-verify loop, which is exactly what an agent team is for.
Agent roster
| Agent | Type | Skill | Output |
|---|---|---|---|
td-architect |
custom | td-feature-design |
_workspace/01_design_<feature>.md |
td-builder (×N) |
custom | td-feature-build |
new tool + test files; _workspace/02_build_<feature>.md |
td-integrator |
custom | td-feature-integrate |
wired index.ts/agent.ts; _workspace/03_integrate.md |
td-qa |
custom | td-feature-qa |
_workspace/04_qa_<batch>.md (PASS/FAIL/UNVERIFIED) |
td-releaser |
custom | td-feature-release |
CHANGELOG + version bump + commit/tag/push; _workspace/05_release.md |
All Agent / TeamCreate calls use model: "opus".
Workflow
Phase 0 — context check (follow-up support)
- Check whether
_workspace/exists. - Decide the run mode:
- No
_workspace/→ fresh run. Go to Phase 1. _workspace/exists + user asks to fix/continue/re-run part → partial re-run. Re-invoke only the affected agent(s), passing the prior artifact paths so they refine rather than rewrite._workspace/exists + a new batch of ideas → new run. Move the old_workspace/to_workspace_<YYYYMMDD_HHMMSS>/, then Phase 1.
- No
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.
- 12d ago First seen · 117 lines · 128 tokens per session scan A 5ab871c2dba7
tdmcp-pipeline is a skill published in the GitHub repository lucasmaher-hash/touch-designer-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 128 tokens to every session and 2,193 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to tdmcp-pipeline, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…