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 AgentsKit-io/doc-bridge --skill doc-bridge-handoffgit clone --depth 1 https://github.com/AgentsKit-io/doc-bridgeWrote 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/agentskit-io/doc-bridge/doc-bridge-handoff)<a href="https://agentmods.dev/skills/agentskit-io/doc-bridge/doc-bridge-handoff"><img src="https://agentmods.dev/badge/skills/agentskit-io/doc-bridge/doc-bridge-handoff.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.00014 | $0.00360 |
| Opus 5 | $0.00007 | $0.00180 |
| Sonnet 5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
doc-bridge-handoff 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 7d 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.
What it actually says
Doc Bridge handoff
Use this skill before editing a repository that contains doc-bridge.config.json.
- Resolve the package or ownership id that best matches the requested change:
- Prefer the read-only MCP tool
handoff.resolvewhen it is available. - Otherwise run
node <skill-directory>/scripts/resolve-handoff.mjs <id>from the repository.
- Prefer the read-only MCP tool
- Read every file in
readBeforeEditing, beginning withstartHere. - Keep changes inside
editRoots. If the requested path is not covered, stop and report the missing route instead of guessing. - Make the smallest change that satisfies the request.
- Run every command in
checksbefore claiming completion. - If documentation changed, refresh the Doc Bridge index and run its gate.
If resolution fails, returns incomplete fields, or names an unknown target, stop. Do not infer edit permission from repository layout.
The resolver and MCP tools are read-only. They resolve project guidance but never authorize edits, publish changes, execute returned checks, or replace repository instructions. The skill uses no credentials and has no provider, hosted service, or AKOS dependency.
Portable runtimes
This directory follows the open Agent Skills layout: one SKILL.md plus optional scripts and fixtures. It can be loaded as a local skill by OpenClaw-compatible clients, Hermes Agent, Pi, Cursor, or another runtime that supports Agent Skills and shell execution. Runtime-specific publication metadata is intentionally kept outside the skill.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 33 lines · 14 tokens per session scan A 595a3d8a96f2
doc-bridge-handoff is a skill published in the GitHub repository AgentsKit-io/doc-bridge (7 stars, last pushed 5d ago), licensed MIT. It adds 14 tokens to every session and 360 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
developer-marketing-playbook
Complete developer marketing playbook covering DevRel programs, documentation as marketing, API developer experience, community building, and hackathon strategy. For dev-tool founders who need to reach engineers. Follow @WeiYipei on X.
README 文档生成
Use this skill to create or improve README content. Cover what the project does, setup, common commands, configuration, development workflow, and troubleshooting.
API 文档自动生成
An API documentation generator that uses interfaces, data types, and examples to produce structured reference material. API means the defined way software programs communicate with each other.
doc-standards
Documentation writing-quality standards — controlled language (ASD-STE100), Google/Microsoft style guide rules, ISO 24495 plain language, AI/agent readability (llms.txt, self-contained sections), and a machine-checkable lint gate. Use whenever writing or reviewing ANY documentation prose — README, API reference…
harness
Route Harness Starter Kit workflows. Use when the user invokes /harness with adopt, doctor, update, refresh, review, or review sub-agent, or asks to apply, diagnose, maintain, or review repository harness guidance.
harness-adopt
Apply Harness Starter Kit prompt-first adoption to a target repository. Use when the user asks to apply, install, adopt, or bootstrap repository harness guidance, checks, memory, and adoption reporting.