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 skills add Cavendo-AI/vantage --skill vantage-shared-intelgit clone --depth 1 https://github.com/Cavendo-AI/vantageWrote 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/cavendo-ai/vantage/vantage-shared-intel)<a href="https://agentmods.dev/skills/cavendo-ai/vantage/vantage-shared-intel"><img src="https://agentmods.dev/badge/skills/cavendo-ai/vantage/vantage-shared-intel.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.1 | $0.00080 | $0.00873 |
| Opus 5 | $0.00040 | $0.00436 |
| Sonnet 5 | $0.00016 | $0.00175 |
| Haiku 4.5 | $0.00008 | $0.00087 |
Grade A, and why
vantage-shared-intel scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS -X POST "$VANTAGE_API_URL/api/signals" \ How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vantage Shared Intel
Use Vantage as the canonical external-intel store. Keep this skill focused on operational workflows:
- ingest signal
- retrieve signal(s)
- summarize + action
- keep data portable across AI clients
Required inputs
Set these in shell commands (or source from env):
VANTAGE_API_URL(example:http://localhost:3020)VANTAGE_API_KEY(vtg_...)
Example:
export VANTAGE_API_URL="http://localhost:3020"
export VANTAGE_API_KEY="vtg_..."
Core workflows
1) Capture a signal
Use when user says "save this", "track this post/article", "add this intel".
curl -sS -X POST "$VANTAGE_API_URL/api/signals" \
-H 'Content-Type: application/json' \
-H "Authorization: Bearer $VANTAGE_API_KEY" \
-d '{
"signalType": "post",
"platform": "x",
"content": "<signal text>",
"sourceUrl": "https://...",
"importance": "high",
"topics": ["AI Agents", "Pricing"]
}'
Capture standards:
- Always include
platform,content,sourceUrlwhen known - Add 1-3
topics - Set
importance(critical|high|normal|low)
2) Search existing intel
Use when user asks "what do we already know about X?".
curl -sS "$VANTAGE_API_URL/api/signals/search?q=<query>" \
-H "Authorization: Bearer $VANTAGE_API_KEY"
Optional filtered listing:
curl -sS "$VANTAGE_API_URL/api/signals?platform=x&importance=high&limit=20" \
-H "Authorization: Bearer $VANTAGE_API_KEY"
3) Get digest/dashboard summary
Use for daily/weekly briefs.
curl -sS "$VANTAGE_API_URL/api/dashboard/summary?period=7d" \
-H "Authorization: Bearer $VANTAGE_API_KEY"
Then provide:
- top topics
- top sources/platforms
- notable high/critical signals
- suggested next actions
4) Bootstrap key (first local setup)
Only for first-time setup:
curl -sS -X POST "$VANTAGE_API_URL/api/auth/keys" \
-H 'Content-Type: application/json' \
-d '{"name":"openclaw"}'
Note:
- first key bootstrap works localhost-only unless
X-Vantage-Bootstrap-Tokenis configured - key is returned once; tell user to store it securely
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.
- 7d ago First seen · 120 lines · 80 tokens per session scan A df02869fea2d
vantage-shared-intel is a skill published in the GitHub repository Cavendo-AI/vantage (1 stars, last pushed 5mo ago), licensed MIT. It adds 80 tokens to every session and 873 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
9router-web-search
Web and X search via 9Router /v1/search using Tavily / Exa / Brave / Serper / SearXNG / Google PSE / Linkup / SearchAPI / You.com / Perplexity / Xquik. Use when the user wants to search the web, find articles, or search public X posts.
9router-stt
Speech-to-text via 9Router /v1/audio/transcriptions using OpenAI Whisper / Groq / Gemini / Deepgram / AssemblyAI / NVIDIA / HuggingFace models. Use when the user wants to transcribe audio, convert speech to text, or get subtitles from audio files.
9router-web-fetch
Fetch URL → markdown / text / HTML via 9Router /v1/web/fetch using Ollama Cloud / Firecrawl / Jina Reader / Tavily Extract / Exa Contents. Use when the user wants to scrape a webpage, extract URL content, read article, or convert a URL to markdown.
9router-embeddings
Generate vector embeddings via 9Router /v1/embeddings using OpenAI / Gemini / Mistral / Voyage / Nvidia / GitHub embedding models for RAG, semantic search, similarity. Use when the user wants embeddings, vectors, RAG, semantic search, or to embed text.
cross-campaign
Discover and reference other camps, projects, and files across camp boundaries. Use when the user mentions another camp or campaign by name, references work done "in another project/camp", or needs to find/copy/compare code across camps.
verify
Fact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.