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/voltagent/skills/voltagent-docs-bundlenpx skills add VoltAgent/skills --skill voltagent-docs-bundlegit clone --depth 1 https://github.com/VoltAgent/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.00039 | $0.00500 |
| Opus 5 | $0.00019 | $0.00250 |
| Sonnet 5 | $0.00008 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
voltagent-docs-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 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.
What it actually says
VoltAgent Embedded Docs Lookup
Look up VoltAgent docs embedded in node_modules/@voltagent/core/docs. This bundle mirrors the website docs plus additional doc sets, so it is safe to use for version-matched answers.
Where the Docs Live
node_modules/@voltagent/core/docs/
|-- actions.md
|-- agents/
|-- api/
|-- blog/
|-- community/
|-- deployment-docs/
|-- deployment.md
|-- evals.md
|-- evaluation-docs/
|-- getting-started/
|-- guardrails/
|-- integrations/
|-- models-docs/
|-- observability/
|-- observability-platform/
|-- prompt-engineering-docs/
|-- rag/
|-- recipes/
|-- repo-docs/
|-- site-examples/
|-- tools/
|-- triggers.md
|-- troubleshooting/
|-- ui/
|-- utils/
`-- workflows/
If you are inside the VoltAgent monorepo, the same content exists at:
packages/core/docs/
Lookup Flow
- List available sections:
ls node_modules/@voltagent/core/docs
- Search for a topic:
rg -n "workflow" node_modules/@voltagent/core/docs -g"*.md"
- Read the file:
cat node_modules/@voltagent/core/docs/workflows/overview.md
Quick Commands
# List docs
ls node_modules/@voltagent/core/docs
# Find a keyword
rg -n "memory" node_modules/@voltagent/core/docs -g"*.md"
# Open a section
cat node_modules/@voltagent/core/docs/getting-started/quick-start.md
Why This Works
- Docs are bundled with the installed version
- Avoids web drift and outdated content
- Covers the full doc surface (guides, recipes, platform docs)
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 · 98 lines · 39 tokens per session scan A 5bf9482fb2b7
voltagent-docs-bundle is a skill published in the GitHub repository VoltAgent/skills (15 stars, last pushed 7mo ago), licensed MIT. It adds 39 tokens to every session and 500 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…