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 skills add hybridlabor-api/bdb-dev-optimized-agent-skills --skill tdmcp-submissiongit 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/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-submission)<a href="https://agentmods.dev/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-submission"><img src="https://agentmods.dev/badge/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-submission/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/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-submission"><img src="https://agentmods.dev/badge/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-submission.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.00130 | $0.01264 |
| Opus 5 | $0.00065 | $0.00632 |
| Sonnet 5 | $0.00026 | $0.00253 |
| Haiku 4.5 | $0.00013 | $0.00126 |
Grade A, and why
tdmcp-submission 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 12d 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
97% identical to tdmcp-submission — 2 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tdmcp submission orchestrator
Coordinates four agents to prepare (and re-prepare) tdmcp's submission to the Anthropic Connectors Directory via the Desktop Extension (MCPB) path. Defines who works when; each agent's skill defines how.
Execution mode — sub-agents (this environment has no TeamCreate)
TeamCreate/SendMessage are not available here, so run agents as
sub-agents with the Agent tool. For every agent:
subagent_type: "general-purpose",model: "opus".- Prompt MUST tell it to read its definition file in
.codex/agents/*.tomland its required skill(s) first, then do the task. Use this exact mapping:architect→.codex/agents/submission-architect.toml,docs-author→.codex/agents/docs-author.toml,bundle-engineer→.codex/agents/bundle-engineer.toml, andsubmission-qa→.codex/agents/submission-qa.toml. The definition file is the source of truth (reusable next session); the prompt just points at it + passes the task and the relevant_workspace/paths. - Parallelize independent agents by sending multiple
Agentcalls in one message (orrun_in_background: true).
Data passing — file-based via _workspace/
Create _workspace/ at the repo root for inter-agent artifacts:
00_submission-spec.md— architect → everyone01_migration-notes.md— bundle-engineer → QA/human02_form-answers.md— docs-author → QA/human (paste-ready form draft)03_qa-report.md— QA → human
Final deliverables (privacy page, edited repo files, tdmcp.mcpb) land in the
repo proper. _workspace/ is preserved for audit / re-runs.
Phase 0: context check (initial vs re-run)
- If
_workspace/is absent → initial run: full pipeline below. - If
_workspace/exists and the user asks to fix/update one part → partial re-run: re-invoke only the affected agent(s), pass the prior artifacts + the new feedback (e.g. a directory rejection reason). E.g. "privacy page rejected" → docs-author only, then QA. - If
_workspace/exists and the user gives fresh inputs → move it to_workspace_prev/and start a new initial run.
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.
- 12d ago First seen · 91 lines · 130 tokens per session scan A 3aa600ceb1a6
tdmcp-submission is a skill published in the GitHub repository hybridlabor-api/bdb-dev-optimized-agent-skills (6 stars, last pushed 7d ago), licensed Apache-2.0. It adds 130 tokens to every session and 1,264 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to tdmcp-submission, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
agent-workflow-automation
Agent skill for workflow-automation - invoke with $agent-workflow-automation.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-pseudocode
Agent skill for pseudocode - invoke with $agent-pseudocode.
agent-trading-predictor
Agent skill for trading-predictor - invoke with $agent-trading-predictor.
agent-performance-analyzer
Agent skill for performance-analyzer - invoke with $agent-performance-analyzer.
embeddings
Vector embeddings with HNSW indexing, sql.js persistence, and hyperbolic support. 75x faster with agentic-flow integration. Use when: semantic search, pattern matching, similarity queries, knowledge retrieval. Skip when: exact text matching, simple lookups, no semantic understanding needed.