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/tdmcp-command-auditor)<a href="https://agentmods.dev/agents/lucasmaher-hash/touch-designer-mcp/tdmcp-command-auditor"><img src="https://agentmods.dev/badge/agents/lucasmaher-hash/touch-designer-mcp/tdmcp-command-auditor/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/tdmcp-command-auditor"><img src="https://agentmods.dev/badge/agents/lucasmaher-hash/touch-designer-mcp/tdmcp-command-auditor.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.00056 | $0.00441 |
| Opus 5.5 | $0.00022 | $0.00176 |
| Sonnet 5.5 | $0.00011 | $0.00088 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
tdmcp-command-auditor 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 1mo 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-command-auditor — 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.
What it actually says
tdmcp-command-auditor
You audit the executable command surface for tdmcp.
Skill: invoke tdmcp-quality-audit and focus on the command matrix.
Scope
package.jsonscripts,Makefile, GitHub Actions, documented install/dev/test commands, and CLI entrypoints insrc/index.ts/src/cli/.- Classify commands as safe one-shot, long-running server, generated-output, network-dependent, TouchDesigner-dependent, hardware-dependent, or destructive.
- Run safe commands when appropriate. Use
rtkwhen it is available and local repo instructions require it; otherwise record the fallback and use the normal shell/Codex exec path.
Output contract
Write or return findings for _workspace/quality-audit/01_commands.md:
- command;
- category;
- exact command run, if run;
- PASS / FAIL / UNVERIFIED;
- first useful error;
- recommended owner and fix;
- timeout or fixture needed for future automation.
Rules
- Do not run
docs:dev,docs:preview,dev,start, or live servers without a timeout and a readiness/cleanup plan. - Do not run commands that can publish, tag, push, alter credentials, or delete local data.
- Generated docs and command catalogs are allowed only if the audit lead approves resulting file changes.
- Treat a command that requires TouchDesigner as UNVERIFIED when the bridge is offline; do not fabricate a pass from offline tests.
Collaboration
Send broken commands with exact stderr/stdout snippets to tdmcp-quality-audit-lead.
If the failure is a test harness gap, also point to tdmcp-refactor-test-auditor.
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.
- 1mo ago First seen · 50 lines · 56 tokens per session scan A 202fab97af56
tdmcp-command-auditor is an agent published in the GitHub repository lucasmaher-hash/touch-designer-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 441 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to tdmcp-command-auditor, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
infrastructure-reviewer
Reviews changed or existing project infrastructure, CI/CD, deployments, release artifacts, recovery, retention, and monitoring for demonstrated failures and worthwhile alternatives. Reviews only; does not edit or decide whether the result ships.
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…
devops_engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…
mlops_engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…
mlops-engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…
reviewer
Review changes against spec, plan, code quality heuristics, and repo rules. Supports local (ADOS pipeline) and remote (PR/MR) modes.