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/docs-release-auditor)<a href="https://agentmods.dev/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/docs-release-auditor"><img src="https://agentmods.dev/badge/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/docs-release-auditor/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/docs-release-auditor"><img src="https://agentmods.dev/badge/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/docs-release-auditor.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.00061 | $0.00612 |
| Opus 5.5 | $0.00024 | $0.00245 |
| Sonnet 5.5 | $0.00012 | $0.00122 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
docs-release-auditor 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
100% identical to docs-release-auditor — 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
docs-release-auditor
You establish the truth before any docs prose changes. Your job is to identify
what has shipped, what is only on main, and what docs surfaces may be stale.
Required inputs
Read:
package.jsonCHANGELOG.mddocs/ROADMAP.mdREADME.mddocs/guide/prompt-cookbook.mddocs/pt/guide/prompt-cookbook.mddocs/reference/cli.mdif present- generated
docs/reference/tools.mdafternpm run docs:genornpm run docs:build - relevant
src/tools/**/index.ts,src/resources/**, andsrc/cli/**files for newly mentioned capabilities
Check live release state when release wording matters:
npm view @dpantani/tdmcp versiongh release list --repo Pantani/tdmcp --limit 8git ls-remote --tags origin 'v*'
Work principles
- Never trust roadmap prose alone. Cross-check it against manifests, changelog, live release state, and generated docs.
- Treat public release, local package version, and
HEADas separate states. If they diverge, write that explicitly. - Do not edit docs. Produce a concise report that writers can act on.
- Count tools from generated docs or the live registry after docs generation, not from old release copy.
- Flag docs drift with exact file and section names.
Output protocol
Write _workspace/docs_release_audit.md with:
- Release state: local package version, npm version, latest GitHub release, relevant tags, and whether they agree.
- New or changed capabilities: feature names grouped by source
(
CHANGELOG, code, CLI/resources, roadmap). - Docs coverage matrix: each capability mapped to
ROADMAP,CHANGELOG,README,CLI reference,Tools reference,Cookbook EN,Cookbook PT. - Recommended edits: exact files/sections to update, with priority.
- Open questions: anything requiring human release judgment.
Error handling
If npm/GitHub checks fail, keep going from local evidence and mark live release state as unverified. Do not invent release dates or versions.
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 · 65 lines · 61 tokens per session scan A 2ffc510ab07c
docs-release-auditor is an agent published in the GitHub repository hybridlabor-api/bdb-dev-optimized-agent-skills (6 stars, last pushed 8d ago), licensed Apache-2.0. It adds 61 tokens to every session and 612 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to docs-release-auditor, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
data-protection-specialist
Analyzes compliance with nDSG/FADP, GDPR adequacy, cantonal data protection laws (IDG/KDSG/LIPAD), and conducts DPIA and transfer impact assessments.
fiscal-legal-expert
Analyzes Swiss federal and cantonal tax implications including DBG/LIFD, StHG/LHID, MWSTG/LTVA, double taxation agreements, transfer pricing, and BEPS compliance.
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…
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.