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/ldclabs/anda-bot/doc-coauthoringnpx skills add ldclabs/anda-bot --skill doc-coauthoringgit clone --depth 1 https://github.com/ldclabs/anda-botWrote 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/ldclabs/anda-bot/doc-coauthoring)<a href="https://agentmods.dev/skills/ldclabs/anda-bot/doc-coauthoring"><img src="https://agentmods.dev/badge/skills/ldclabs/anda-bot/doc-coauthoring.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 | $0.00064 | $0.01834 |
| Opus 5 | $0.00032 | $0.00917 |
| Sonnet 5 | $0.00013 | $0.00367 |
| Haiku 4.5 | $0.00006 | $0.00183 |
Grade A, and why
doc-coauthoring 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 4d 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc Co-Authoring Workflow
This skill guides collaborative document creation in Anda Bot. Act as an active co-author through three stages:
- Context Gathering
- Refinement and Structure
- Reader Testing
Use the current conversation, attached files, local workspace files, available tools, and optional subagents. Do not assume a hosted document editor, product-specific connectors, or platform-specific editing tools exist.
When to Offer This Workflow
Offer this workflow when the user starts a substantial writing task, including:
- "write a doc", "draft a proposal", "create a spec", "write this up"
- "PRD", "design doc", "decision doc", "RFC", "technical spec"
- editing or reorganizing an existing document
Briefly explain the three stages:
- Context Gathering: collect the facts, constraints, audience, and open questions.
- Refinement and Structure: build the document section by section, with the user choosing what to keep, remove, or combine.
- Reader Testing: test whether a fresh reader can answer likely questions from the document alone.
Ask whether the user wants the structured workflow or a freer collaboration. If they decline, work freeform.
Stage 1: Context Gathering
Goal: close the gap between what the user knows and what Anda Bot has in the conversation, so later drafting is grounded instead of generic.
Initial Questions
Start with concise meta-context questions:
- What type of document is this?
- Who is the primary audience?
- What should change after someone reads it?
- Is there a template, style, repo convention, or target format?
- Are there constraints such as deadline, length, approval path, or source material?
Tell the user they can answer in shorthand or dump information in any order.
Source Material
If the user references existing material:
- For local files or attached files, read them with available file tools.
- For repository docs, search with
rgor available search tools before drafting. - For URLs or external systems, use available network, browser, integration, or shell tools only if they are present and appropriate. If not, ask the user to paste the relevant content or provide local exports.
- For images in a document, check whether the document relies on visual content that text-only readers would miss. Ask for or generate alt-text when useful.
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.
- 4d ago First seen · 248 lines · 64 tokens per session scan A c7692233aaf4
doc-coauthoring is a skill published in the GitHub repository ldclabs/anda-bot (23 stars, last pushed 27d ago), licensed Apache-2.0. It adds 64 tokens to every session and 1,834 once invoked, about $0.0003 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…