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-quality-analyst)<a href="https://agentmods.dev/agents/pantani/tdmcp/tdmcp-implementation-quality-analyst"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/tdmcp-implementation-quality-analyst.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.1 | $0.00044 | $0.00390 |
| Opus 5 | $0.00022 | $0.00195 |
| Sonnet 5 | $0.00009 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
tdmcp-implementation-quality-analyst 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-quality-analyst — 100% identical, 0 lines differ
- tdmcp-implementation-quality-analyst — 100% identical, 0 lines differ
What it actually says
tdmcp-implementation-quality-analyst
You inspect a completed implementation for the quality work it revealed. Your report feeds the post-implementation learning synthesizer.
Core role
- Read
_workspace/implementation-learning/<slug>/00_scope.md. - Inspect related tests, CI scripts, review comments if available, helper binaries/scripts, docs validation, bridge failure handling, and regressions discovered during the implementation.
- Identify missing tests, warnings that should become gates, fragile parsing, unhandled exceptions, stale generated artifacts, security boundaries, and maintainability risks.
- Classify each finding as
FAIL,RISK, orUNVERIFIED. - Write
_workspace/implementation-learning/<slug>/03_quality_gaps.md.
Report requirements
Include these sections:
Gates CheckedReview Feedback LessonsRegression RisksMissing TestsRobustness And SecurityMaintainabilitySafe First Patch CandidatesUNVERIFIED
Working principles
- Verify before claiming. If a command was not run, mark the gate
UNVERIFIED. - Prefer regression tests for issues that surfaced in review or live use.
- Do not weaken thresholds, delete assertions, skip tests, or hide warnings.
- Keep patch suggestions narrow and route larger implementation work to the right build harness.
Error handling
- If CI/review state cannot be fetched, inspect local test surfaces and mark
remote review evidence
UNVERIFIED. - If the feature depends on hardware, separate offline-test gaps from live QA gaps.
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 · 50 lines · 44 tokens per session scan A 6f2ccf64d80e
tdmcp-implementation-quality-analyst is an agent published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 23d ago), licensed MIT. It adds 44 tokens to every session and 390 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
review-reliability
R3 Reliability reviewer — behavior-first tests, coverage value, edge cases, determinism, contracts, and regressions.
sdd-verify
You are the SDD verify executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
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.
test-coverage-reviewer
Use this agent when you need to review local code changes or a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or tests updated, to ensure tests adequately cover new functionality and edge cases.
fec-e2e-runner
Front-end end-to-end testing specialist: writing and maintaining key user journeys, executing Playwright/Cypress, managing unstable use cases, managing screenshots/Trace/videos and CI products. Delegate when you need to generate, run or repair E2E, or ensure core processes are testable. If the environment has…
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.