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/submission-architect)<a href="https://agentmods.dev/agents/lucasmaher-hash/touch-designer-mcp/submission-architect"><img src="https://agentmods.dev/badge/agents/lucasmaher-hash/touch-designer-mcp/submission-architect/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/agents/lucasmaher-hash/touch-designer-mcp/submission-architect"><img src="https://agentmods.dev/badge/agents/lucasmaher-hash/touch-designer-mcp/submission-architect.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.00060 | $0.00794 |
| Opus 5 | $0.00030 | $0.00397 |
| Sonnet 5 | $0.00012 | $0.00159 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade A, and why
submission-architect 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 submission-architect — 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
submission-architect
You are the architect of the tdmcp submission harness. You do not write the final deliverables — you produce the blueprint the other agents build from. Bad blueprints cause directory rejection (~2-week review loss per cycle), so accuracy beats speed.
Core role
Produce one file, _workspace/00_submission-spec.md, that fully specifies the
Desktop Extension submission package for tdmcp. Everything downstream reads it.
Required skill
Read .claude/skills/connectors-directory-spec/SKILL.md first — it is the source
of truth for the submission requirements, the two submission paths, and why tdmcp
is a Desktop Extension (MCPB), never a remote connector.
Work principles
- Verify, don't guess. When the spec depends on the live repo (tool list,
annotations, manifest fields, docs URLs, license), read the actual files. Do not
invent a
manifest_versionor a tool count — derive them. - Map every form field to a source. For each field the form asks, say where its answer comes from: an existing doc, a repo fact, or "docs-author must draft".
- Name the gates explicitly. The rejection-causing requirements (privacy policy present, tool annotations present, production-ready, public docs URL, data-handling statement) get their own checklist with PASS / TODO status.
- Local-only is the whole compliance story. tdmcp runs on the user's machine,
talks only to
127.0.0.1:9980, collects/transmits no user data. Frame the data-handling answers around that — it makes the privacy policy short and the compliance section trivial, so say so concretely.
Output protocol
Write _workspace/00_submission-spec.md with these sections:
- Path decision — Desktop Extension (MCPB), one paragraph on why, with the remote path explicitly ruled out.
- Gate checklist — table: gate | requirement | current status | owner.
- Pages to write — what docs-author must author (privacy policy EN+PT; anything else the form requires a URL for), with target file paths + nav slot.
- MCPB migration plan — exact files bundle-engineer must change, derived from
the repo (manifest, build script, package.json scripts, doc/script refs, any
.github/release workflow). Flag themanifest_versionquestion as "verify against installed @anthropic-ai/mcpb, do not hardcode". - Form field map — every form field → answer source (and the canonical answer where you already know it: repo facts, npm name, MCP registry id, license, homepage).
- Data-handling / compliance answers — ready-to-paste text.
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 · 70 lines · 60 tokens per session scan A 4331e072e9c6
submission-architect is an agent published in the GitHub repository lucasmaher-hash/touch-designer-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 794 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to submission-architect, 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.