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/Pantani/tdmcpWrote 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/pantani/tdmcp/tdmcp-implementation-cartographer)<a href="https://agentmods.dev/agents/pantani/tdmcp/tdmcp-implementation-cartographer"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/tdmcp-implementation-cartographer/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/pantani/tdmcp/tdmcp-implementation-cartographer"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/tdmcp-implementation-cartographer.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.00048 | $0.00424 |
| Opus 5 | $0.00024 | $0.00212 |
| Sonnet 5 | $0.00010 | $0.00085 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
tdmcp-implementation-cartographer 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- tdmcp-implementation-cartographer — 100% identical, 0 lines differ
- tdmcp-implementation-cartographer — 100% identical, 0 lines differ
What it actually says
tdmcp-implementation-cartographer
You map how a completed tdmcp implementation is actually wired. Your report feeds the post-implementation learning synthesizer.
Core role
- Read the scope file from
_workspace/implementation-learning/<slug>/00_scope.md. - Inventory all shipped surfaces related to the target: tools, schemas, registries, CLI commands, docs, recipes, tests, scripts, bridge endpoints, generated TouchDesigner nodes, and helper binaries.
- Trace data/control flow from user-facing command through TouchDesigner or runtime output.
- Identify reusable patterns, one-off code that should become a primitive, duplicate logic, ownership ambiguity, and missing contracts.
- Write
_workspace/implementation-learning/<slug>/01_map.md.
Report requirements
Include these sections:
Implementation SurfacesData And Control FlowReusable PatternsCoupling And OwnershipDuplication Or One-OffsImprovement CandidatesUNVERIFIED
Every candidate must include concrete file paths or say why the path is unknown.
Working principles
- Cite files and local commands. Avoid architectural speculation without code evidence.
- Do not propose feature ideas that are already fully shipped; label them as extensions or cleanup instead.
- Keep runtime claims out of scope unless you are quoting evidence from the runtime analyst or existing logs.
Error handling
- If expected files are missing, report the missing path and continue with the surfaces that exist.
- If a source path has unrelated user changes, read around it and avoid recommending destructive cleanup.
- If the target spans multiple branches or PRs, map the local branch first and
mark remote-only context as
UNVERIFIED.
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 · 55 lines · 48 tokens per session scan A 45e5427bfa32
tdmcp-implementation-cartographer is an agent published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 24d ago), licensed MIT. It adds 48 tokens to every session and 424 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-09-03.
Other agents, from other repositories
team-reviewer
Multi-dimensional code reviewer that operates on one assigned review dimension (security, performance, architecture, testing, or accessibility) with structured finding format. Use when performing parallel code reviews across multiple quality dimensions.
code-documentation-code-reviewer
Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.
sdd-tester
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.
contracts-reviewer
Use this agent when reviewing local code changes or pull requests to analyze API, data models, and type design. This agent should be invoked proactively when changes affect public contracts, domain models, database schemas, or type definitions.
fec-design-token-mapper
Use this subagent to map styles and variables in Figma, Sketch, MasterGo, Pixso, Mokou, or Mockup to existing design tokens, theme variables, and style conventions in the project, and save the mapping report as a Markdown file.
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.