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 agentmods add skills/afk-surf/openbridge/docsnpx skills add AFK-surf/OpenBridge --skill docsgit clone --depth 1 https://github.com/AFK-surf/OpenBridgeWhat 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 | $0.00011 | $0.01091 |
| Opus 5 | $0.00005 | $0.00545 |
| Sonnet 5 | $0.00002 | $0.00218 |
| Haiku 4.5 | $0.00001 | $0.00109 |
Grade A, and why
docs 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 2d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DOCX reading, creation, editing, and review guidance
Workflow Decision
| Task | Tool | Reference |
|---|---|---|
| Reading/analyzing content | soffice + pdftoppm | See "Reading DOCXs" below |
| Creating new documents | python-docx | See "Primary tooling" below |
| Editing with tracked changes | OOXML XML manipulation | ooxml-editing.md |
| Adding comments | OOXML XML manipulation | ooxml-editing.md |
Reading DOCXs
- Use
soffice -env:UserInstallation=file:///tmp/lo_profile_$$ --headless --convert-to pdf --outdir $OUTDIR $INPUT_DOCXto convert DOCXs to PDFs.- The
-env:UserInstallation=file:///tmp/lo_profile_$$flag is important. Otherwise, it will time out.
- The
- Then Convert the PDF to page images so you can visually inspect the result:
pdftoppm -png $OUTDIR/$BASENAME.pdf $OUTDIR/$BASENAME
- Then open the PNGs and read the images.
- Only do python printing as a last resort because you will miss important details with text extraction (e.g. figures, tables, diagrams).
Primary tooling for creating DOCXs
- Create and edit DOCX files with
python-docx. Use it to control structure, styles, tables, and lists. Install it withpip install python-docxif it's not already installed. - After every meaningful batch of edits—new sections, layout tweaks, styling changes—render the DOCX to PDF:
soffice -env:UserInstallation=file:///tmp/lo_profile_$$ --headless --convert-to pdf --outdir $OUTDIR $INPUT_DOCX
- Convert the PDF to page images so you can visually inspect the result:
pdftoppm -png $OUTDIR/$BASENAME.pdf $OUTDIR/$BASENAME
- Inspect every PNG before moving on. If you see any defect, fix the DOCX and repeat the render → inspect loop until all pages look perfect.
What ships with it
2 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.
- 2d ago First seen · 67 lines · 11 tokens per session scan A 132e507f6c3c
docs is a skill published in the GitHub repository AFK-surf/OpenBridge (424 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 1,091 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…