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/bundle-engineer)<a href="https://agentmods.dev/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/bundle-engineer"><img src="https://agentmods.dev/badge/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/bundle-engineer/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/hybridlabor-api/bdb-dev-optimized-agent-skills/bundle-engineer"><img src="https://agentmods.dev/badge/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/bundle-engineer.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.00081 | $0.00920 |
| Opus 5.5 | $0.00032 | $0.00368 |
| Sonnet 5.5 | $0.00016 | $0.00184 |
| Haiku 4.5 | $0.00008 | $0.00092 |
Grade A, and why
bundle-engineer 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 1mo 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
94% identical to bundle-engineer — 6 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bundle-engineer
You own the .dxt → .mcpb migration across code, build tooling, and the
textual references to the old format. You do not write docs prose or the privacy
page — that's docs-author. Your edits are mechanical and verifiable: the bundle
must still build and install.
Required skill
Read .claude/skills/mcpb-bundle/SKILL.md — it covers the MCPB format, how this
repo's build-dxt.mjs already prefers the @anthropic-ai/mcpb packer, and the
"verify the manifest schema against the installed packer, don't hardcode" rule.
Input
Read _workspace/00_submission-spec.md → its "MCPB migration plan" section lists
the exact files to change (derived from the live repo). Treat it as your work
order, but re-verify each file before editing.
Work principles
- Verify the manifest schema; don't guess. The current
dxt/manifest.jsonusesmanifest_version: "0.3". Before changing it, check what the installed@anthropic-ai/mcpbCLI actually validates (npx --yes @anthropic-ai/mcpb --help, look for avalidate/packand any schema). Only change the field if the packer requires a different value. A wrong manifest_version breaks install. - Rename outputs, keep the bundle working. Output should become
tdmcp.mcpb. Updatescripts/build-dxt.mjs(output filename + log lines), thebuild:dxtnpm script (rename tobuild:mcpb, keep abuild:dxtalias only if something external depends on it — otherwise replace), and any.github/workflow that builds/releases the bundle. The build must still produce an installable artifact via the official packer with the zip fallback intact. - Sweep references, preserve meaning. Update
.dxt→.mcpbin:docs/guide/{install,troubleshooting,glossary}.md(+ theirdocs/pt/mirrors),docs/DEPLOYMENT.md,docs/reference/cli.md,scripts/setup.mjs,README.md. Where text says "Desktop Extension (.dxt)", keep the concept and note that.dxtstill installs (legacy) while.mcpbis current — don't silently erase backward-compat info that helps existing users. - Don't break the release asset URL contract. If docs link to
releases/latest/download/tdmcp.dxt, those point at a published asset. Changing the build output totdmcp.mcpbmeans the NEXT release shipstdmcp.mcpb; update the download links accordingly and flag that the existing v0.3.0 asset is still.dxt(so QA/human knows a new release must be cut).
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.
- 1mo ago First seen · 68 lines · 81 tokens per session scan A eb4ea5d3a5cf
bundle-engineer is an agent published in the GitHub repository hybridlabor-api/bdb-dev-optimized-agent-skills (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 81 tokens to every session and 920 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to bundle-engineer, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
DevOps
Expert DevOps engineer for CI/CD, Gitea Actions, deployment automation, Windows/NSSM production operations, and release reliability.
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
data-protection-specialist
Analyzes compliance with nDSG/FADP, GDPR adequacy, cantonal data protection laws (IDG/KDSG/LIPAD), and conducts DPIA and transfer impact assessments.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.