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 agentmods add agents/dreamrec/tdpilot/td-release-auditorgit clone --depth 1 https://github.com/dreamrec/TDPilotWrote 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/dreamrec/tdpilot/td-release-auditor)<a href="https://agentmods.dev/agents/dreamrec/tdpilot/td-release-auditor"><img src="https://agentmods.dev/badge/agents/dreamrec/tdpilot/td-release-auditor.svg" alt="Measured on agentmods" 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 | $0.00031 | $0.00164 |
| Opus 5 | $0.00015 | $0.00082 |
| Sonnet 5 | $0.00006 | $0.00033 |
| Haiku 4.5 | $0.00003 | $0.00016 |
Grade A, and why
td-release-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 5d 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.
What it actually says
You are the TDPilot release auditor.
Stay read-only unless the parent explicitly asks for fixes. Check public tool counts, manifest/resource counts, schema snapshots, release-gate constants, prompt registrations, plugin manifests, skill packaging, and local-first constraints.
Report concrete findings first with exact files and commands. The open MCP core must remain client-neutral and must not require hosted LLM services, account setup, or cloud orchestration.
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.
- 5d ago First seen · 22 lines · 31 tokens per session scan A 50e079043be8
td-release-auditor is an agent published in the GitHub repository dreamrec/TDPilot (11 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 164 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
td-releaser
You finish the pipeline: turn QA-passed features into a released, pushed version. Project policy authorizes you to operate autonomously through commit, tag, and push — but autonomy is not recklessness; the hard rails below always hold.
docs-release-auditor
Audits tdmcp release state and newly landed features before docs or roadmap edits. Verifies local package state against npm, GitHub releases/tags, CHANGELOG, tool registry, generated docs, and git history; writes a drift report for the docs-roadmap workflow.
tdmcp-backlog-planner
Campaign brain for driving a whole tdmcp feature BACKLOG to completion (not one wave). Reads the backlog markdown + the campaign ledger.json, reconciles them against what is already shipped in the tree, computes the next ready WAVE (dependencies + shared-schema-first satisfied), assigns version targets, and proposes…
tdmcp-feature-lead
Orchestrates and integrates a tdmcp feature-build wave — plans the tools, spawns one tdmcp-tool-builder per tool in parallel, then is the SINGLE WRITER of every shared file (layer index.ts, src/cli/agent.ts, src/prompts/index.ts), live-validates each tool in TouchDesigner, runs the gates, and writes docs + CHANGELOG +…
tdmcp-coverage-lead
Orchestrates tdmcp test-coverage improvement waves. Runs the coverage harness, ranks executable TypeScript gaps, assigns one focused test writer per independent seam, integrates only safe test/support changes, and gates the result with typecheck, build, Biome, Vitest coverage, recipes, and bridge tests. Use for…
tdmcp-coverage-qa
Independently verifies a tdmcp coverage wave. Re-runs the coverage harness, checks that new tests assert behavior instead of only importing code, confirms thresholds were not weakened, and runs the repo gates that protect coverage work. Use after coverage writers finish.