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/vibeknow/cli/vibeknow-docnpx skills add vibeknow/cli --skill vibeknow-docgit clone --depth 1 https://github.com/vibeknow/cliWrote 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/vibeknow/cli/vibeknow-doc)<a href="https://agentmods.dev/skills/vibeknow/cli/vibeknow-doc"><img src="https://agentmods.dev/badge/skills/vibeknow/cli/vibeknow-doc.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.00046 | $0.00950 |
| Opus 5 | $0.00023 | $0.00475 |
| Sonnet 5 | $0.00009 | $0.00190 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
vibeknow-doc 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vibeknow-doc
TRIGGER
- Upload a document to vectoria for processing
- Check document processing status
- Get a doc_id for later use with
vibeknow create --from <doc_id>
SKIP
- Video generation or task management → use vibeknow-create
- Auth, profile, environment setup → use vibeknow-core
- RAG queries → not yet available
Core Concepts
- doc upload: Uploads a local file to vectoria. Creates a knowledge base, polls until processing completes, and returns the
doc_id+kb_id. - doc get: Fetches document status from vectoria. Requires both
<doc_id>and--kb-id. - Document states:
processing→completedorfailed. - Relationship to create:
vibeknow create --from <doc_id>uses an already-uploaded document. If you pass a file path or URL tocreate --from, it uploads automatically — you don't needdoc uploadfirst.
Quick Reference
| Command | Description |
|---|---|
vibeknow doc upload <file> |
Upload a document to vectoria |
vibeknow doc get <doc_id> --kb-id <kb_id> |
Fetch document status |
For full flags and output examples, see commands.md.
Common Tasks
Upload a document and get its doc_id
vibeknow doc upload ./report.pdf
# Output includes doc_id and kb_id
vibeknow doc upload ./report.pdf --output json
# {"doc_id":"doc_abc123","kb_id":"kb_xyz789","status":"completed"}
Check if a document is ready
vibeknow doc get doc_abc123 --kb-id kb_xyz789
Upload then create video (two-step)
# Step 1: upload (useful if you want to reuse the doc_id)
result=$(vibeknow doc upload ./slides.pdf --output json)
doc_id=$(echo "$result" | jq -r '.doc_id')
# Step 2: create video from the uploaded doc
vibeknow create --from "$doc_id"
Note: For one-shot workflows, vibeknow create --from ./slides.pdf does both steps automatically.
Exit Code Handling
| Exit | Meaning | Action |
|---|---|---|
| 0 | Success | — |
| 1 | General error | Read stderr |
| 2 | Invalid arguments | Check file path exists, doc_id format |
| 3 | Auth error | Run vibeknow auth status to inspect credential source. Re-login with vibeknow auth login (interactive) or set VIBEKNOW_TOKEN. See vibeknow-core for profile/diagnostics if installed. |
| 130 | User interrupt | — |
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.
- 4d ago First seen · 110 lines · 46 tokens per session scan A 6eb90c571e39
vibeknow-doc is a skill published in the GitHub repository vibeknow/cli (6 stars, last pushed 8d ago), licensed MIT. It adds 46 tokens to every session and 950 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
llamaindex
Data framework for building LLM applications with RAG. Specializes in document ingestion (300+ connectors), indexing, and querying. Features vector indices, query engines, agents, and multi-modal support. Use for document Q&A, chatbots, knowledge retrieval, or building RAG pipelines. Best for data-centric LLM…
potpie-source-ingestion
Use when the user explicitly asks to ingest, refresh, or deeply understand a repository, PR, issue, ticket, runbook, incident report, document, or web link into Potpie. The harness performs todo-driven discovery, uses local/GitHub/integration tools and read-only subagents when available, builds evidence-backed…
kb-retriever
面向本地知识库目录的检索和问答助手。核心流程：(1)分层索引导航 (2)遇到PDF/Excel时必须先读取references学习处理方法 (3)处理文件后再检索。按文件类型组合使用 grep、Read、pdfplumber、pandas 进行渐进式检索，避免整文件加载。用户问题涉及"从知识库目录回答问题/检索信息/查资料"时使用。.
debug-ingestion
Debug haiku.rag ingestion in Logfire. Use when asked to look at Logfire for ingestion, find failed or dead ingestion jobs, investigate retries or circuit-breaker events, trace a document through convert/chunk/embed/store, find which docling-serve instance served a request, spot slow conversions, or tell concurrent…
pdf-markdown-validator
Validate PDF to Markdown conversion quality using multi-dimensional metrics. Assess table accuracy, style preservation (bold/italic/headings), robustness, and performance with standardized F1-scoring methodology.
rag-deep-dive
Three-step multi-tool workflow — search the corpus, fetch the most relevant document in full, then find similar documents. Use when a single searchknowledge hit is not enough because the user asked a "how does X work end to end" or "explain the pattern" or "give me the full picture" question. Prevents shallow answers…