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/hybridlabor-api/bdb-dev-optimized-agent-skillsWrote 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/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-implementation-quality-analyst)<a href="https://agentmods.dev/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-implementation-quality-analyst"><img src="https://agentmods.dev/badge/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/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 4d 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-implementation-quality-analyst — 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-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.
- 4d ago First seen · 50 lines · 44 tokens per session scan A 6f2ccf64d80e
tdmcp-implementation-quality-analyst is an agent published in the GitHub repository hybridlabor-api/bdb-dev-optimized-agent-skills (6 stars, last pushed 2d ago), licensed Apache-2.0. 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. It is 100% identical to tdmcp-implementation-quality-analyst, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Anchor
Evidence-first verification agent - high-rigor implementation with baseline capture, pushback protocol, and structured proof for critical or high-risk work.
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
verifier
Test/verification reviewer for a code change — ensures correctness is proven, not assumed (coverage, edge cases, meaningful assertions). Use when reviewing test quality for a diff/PR.