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-submissiongit 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-submission)<a href="https://agentmods.dev/skills/lucasmaher-hash/touch-designer-mcp/tdmcp-submission"><img src="https://agentmods.dev/badge/skills/lucasmaher-hash/touch-designer-mcp/tdmcp-submission/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-submission"><img src="https://agentmods.dev/badge/skills/lucasmaher-hash/touch-designer-mcp/tdmcp-submission.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.01265 |
| Opus 5 | $0.00065 | $0.00633 |
| Sonnet 5 | $0.00026 | $0.00253 |
| Haiku 4.5 | $0.00013 | $0.00127 |
Grade A, and why
tdmcp-submission 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 11d 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-submission — 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tdmcp submission orchestrator
Coordinates four agents to prepare (and re-prepare) tdmcp's submission to the Anthropic Connectors Directory via the Desktop Extension (MCPB) path. Defines who works when; each agent's skill defines how.
Execution mode — sub-agents (this environment has no TeamCreate)
TeamCreate/SendMessage are not available here, so run agents as
sub-agents with the Agent tool. For every agent:
subagent_type: "general-purpose",model: "opus".- Prompt MUST tell it to read its definition file in
.codex/agents/*.tomland its required skill(s) first, then do the task. Use this exact mapping:architect→.codex/agents/submission-architect.toml,docs-author→.codex/agents/docs-author.toml,bundle-engineer→.codex/agents/bundle-engineer.toml, andsubmission-qa→.codex/agents/submission-qa.toml. The definition file is the source of truth (reusable next session); the prompt just points at it + passes the task and the relevant_workspace/paths. - Parallelize independent agents by sending multiple
Agentcalls in one message (orrun_in_background: true).
Data passing — file-based via _workspace/
Create _workspace/ at the repo root for inter-agent artifacts:
00_submission-spec.md— architect → everyone01_migration-notes.md— bundle-engineer → QA/human02_form-answers.md— docs-author → QA/human (paste-ready form draft)03_qa-report.md— QA → human
Final deliverables (privacy page, edited repo files, tdmcp.mcpb) land in the
repo proper. _workspace/ is preserved for audit / re-runs.
Phase 0: context check (initial vs re-run)
- If
_workspace/is absent → initial run: full pipeline below. - If
_workspace/exists and the user asks to fix/update one part → partial re-run: re-invoke only the affected agent(s), pass the prior artifacts + the new feedback (e.g. a directory rejection reason). E.g. "privacy page rejected" → docs-author only, then QA. - If
_workspace/exists and the user gives fresh inputs → move it to_workspace_prev/and start a new initial run.
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.
- 11d ago First seen · 91 lines · 130 tokens per session scan A 0b57d18ddf75
tdmcp-submission is a skill published in the GitHub repository lucasmaher-hash/touch-designer-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 130 tokens to every session and 1,265 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-submission, 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…