Borrowing it
Nothing to install: this file belongs to butgo/butgo-specdrive-lab. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/butgo/butgo-specdrive-lab/main/.agents/skills/doc-work-bundle/SKILL.mdgit clone --depth 1 https://github.com/butgo/butgo-specdrive-labWrote 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/butgo/butgo-specdrive-lab/doc-work-bundle)<a href="https://agentmods.dev/skills/butgo/butgo-specdrive-lab/doc-work-bundle"><img src="https://agentmods.dev/badge/skills/butgo/butgo-specdrive-lab/doc-work-bundle.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.00038 | $0.02700 |
| Opus 5 | $0.00019 | $0.01350 |
| Sonnet 5 | $0.00008 | $0.00540 |
| Haiku 4.5 | $0.00004 | $0.00270 |
Grade A, and why
doc-work-bundle 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.
How it starts
The opening of the file, as written. The whole thing — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc Work Bundle
Use this skill when a target document should be checked or revised against its configured mutual-impact document bundle.
This skill sits above $doc-work-ref:
$doc-workreads one target document only.$doc-work-refreads the target document plusreference_docsfromaffected-docs-map.jsononly.$doc-work-bundlereads the target document plusbundle_refsfromdoc-work-bundle-map.json.$doc-work-bundleis for mutual consistency checks, not broad impact validation by default.
Read First
Read these registries first:
specdrive/config/target-registry.json
specdrive/config/doc-work-bundle-map.json
If the user did not provide a target key or document path, list bundle entry keys and mapped target keys from doc-work-bundle-map.json and stop.
Resolve the user input against doc-work-bundle-map.json first, then use target-registry.json to enrich metadata when a mapped target key exists.
Find the matching bundle entry by:
- exact bundle entry key
target_keys- target document path after removing the bundle map
base_path - entry
path
If the input matches only target-registry.json, use the target's document_path to find the bundle entry.
If the input matches a bundle entry key, resolve the target document by joining base_path and entry path.
If the user provided only a target and no action, read only the target metadata and bundle entry metadata. Show the action choices.
Supported actions for now:
referencerevise
For reference or revise, read first:
- the resolved target document
- documents listed in that entry's
bundle_refs
Resolve relative path and bundle_refs against the bundle map base_path.
Do not inspect docs/history/** file contents unless the user explicitly asks for history lookup.
Missing optional or future documents should be reported, not invented.
History Rules
If a bundle action updates one document, save one history snapshot and one note for that document.
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 · 325 lines · 38 tokens per session scan A 396cd2af4ab1
doc-work-bundle is a skill published in the GitHub repository butgo/butgo-specdrive-lab (1 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 2,700 once invoked, about $0.0002 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
dcf-model
Build discounted cash flow valuation workbooks in Excel.
comps-analysis
Build comparable-company valuation workbooks in Excel.
lbo-model
Build leveraged buyout workbooks with IRR/MOIC in Excel.
PDF files: create, read, merge, fill, OCR, edit text.
excel-author
Build auditable financial workbooks headless via openpyxl.
siyuan
Query and edit a SiYuan knowledge base via its API.