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 commands/botpress/skills/adk-documentgit clone --depth 1 https://github.com/botpress/skillsWhat 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.00021 | $0.00846 |
| Opus 5 | $0.00010 | $0.00423 |
| Sonnet 5 | $0.00004 | $0.00169 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
adk-document 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load the adk-docs skill for documentation standards and the adk skill for ADK context, then help with documentation immediately.
Parse $ARGUMENTS to determine the action. The first word is usually the action (but not always); everything after is the target.
Route by Action
create [topic]
E.g., /adk-document create workflows, /adk-document create the checkout flow
If the topic is a broad term ("workflows", "tools", "actions"), read src/<relevant-dir>/ to enumerate the user's actual primitives first. Document their specific implementations — not generic concepts.
- Research: Find the user's ADK project (
agent.config.ts), read relevant source files insrc/, check existing docs in./docs/or./guides/. - Choose type: Reference (400-500 lines), Conceptual (500-700), Comprehensive (600-800) — see doc-standards reference.
- Write: Every concept needs a working code example from the user's actual code. Include file paths for verification. Use clear headers for ripgrep searchability. No speculative Common Mistakes or Best Practices sections.
- Save: Ask where if unclear (common:
./docs/,./guides/). Verify headers are searchable.
review [doc-path]
E.g., /adk-document review docs/workflows.md
Review the doc for technical accuracy, searchability, and completeness:
- Code accuracy: correct imports (
@botpress/runtime), examples from actual code with file paths, no speculation - Searchability: clear section headers, TOC present, keyword-rich section names
- ADK-specific: distinguishes ADK vs SDK primitives, messages vs events, channel-specific vs agnostic
- Validation:
Grepfor imports, check referenced files exist, flag speculative content
Report: Critical Issues → Searchability Issues → Speculative Content → Missing Verification → Recommendations.
update [doc-path] [what-changed]
E.g., /adk-document update docs/workflows.md added new step type
- Read the existing doc.
- Find what changed in the user's project code.
- Preserve existing structure, style, and TOC.
- Verify all code examples still work. Add new features with project code examples.
- Mark deprecations clearly. Update file path references.
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 · 77 lines · 21 tokens per session scan A 099931067c9e
adk-document is a command published in the GitHub repository botpress/skills (11 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 846 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.