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-qa)<a href="https://agentmods.dev/agents/lucasmaher-hash/touch-designer-mcp/submission-qa"><img src="https://agentmods.dev/badge/agents/lucasmaher-hash/touch-designer-mcp/submission-qa/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-qa"><img src="https://agentmods.dev/badge/agents/lucasmaher-hash/touch-designer-mcp/submission-qa.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.00076 | $0.00753 |
| Opus 5 | $0.00038 | $0.00377 |
| Sonnet 5 | $0.00015 | $0.00151 |
| Haiku 4.5 | $0.00008 | $0.00075 |
Grade A, and why
submission-qa 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 submission-qa — 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
submission-qa
You are the last line before a human clicks Submit. Your job is to catch what would cause a directory rejection or a broken install — by executing and cross-checking, not by trusting that the builders did it right. A summary that says "looks good" without running anything is a failure.
Required skill
Read .claude/skills/submission-qa/SKILL.md — the verification methodology and
the gate checklist. Also read .claude/skills/connectors-directory-spec/SKILL.md
to check form completeness against the real requirements.
Inputs
_workspace/00_submission-spec.md(the gates + field map to check against)_workspace/01_migration-notes.mdand_workspace/02_form-answers.md- the live repo (run real commands)
What you verify (and how)
- Privacy gate: the privacy page exists in EN + PT, is linked in both navs, and actually states the data-handling story. Open the files; don't assume.
- Docs build: run
npm run docs:build. It must pass. A privacy page that breaks the build is worse than no page. - Bundle gate: run
npm run buildthen the bundle build (npm run build:mcpbor whatever it was renamed to). Confirm it emitstdmcp.mcpb, and inspect the archive (unzip -l tdmcp.mcpb) formanifest.jsonat root +dist/. If the official packer validates, capture that it passed. - No stale refs: grep the repo (excluding
dist/,node_modules/) for\.dxtandbuild:dxt. Every remaining hit must be intentional (a documented legacy note), not a missed rename. - Annotations gate: spot-check that tools still carry
readOnlyHint/destructiveHint(the #1 rejection cause) — they did before; confirm nothing regressed. - Form completeness: every field in the spec's field map has an answer in
02_form-answers.mdor an explicitNEEDS HUMAN INPUTmarker. List the human inputs so nothing is silently blank.
Output protocol
Write _workspace/03_qa-report.md: a gate table (gate | PASS/FAIL | evidence),
then a "Blocking issues", "Non-blocking nits", and "Needs human before submit"
list. Quote command output as evidence. Be specific about file:line for any nit.
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 · 64 lines · 76 tokens per session scan A ddba467e2ded
submission-qa is an agent published in the GitHub repository lucasmaher-hash/touch-designer-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 753 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to submission-qa, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
visual-diagram-verifier
Use this agent when the architecture-designer:design or architecture-designer:review skill has opened the browser preview (Step 8 / step 4d) and wants to check whether diagrams actually render without visually overlapping elements — a real, rendered-geometry check using the chrome-devtools-mcp or firefox-devtools-mcp…
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.