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/wittyreference/twilio-claude-plugin/context-hubnpx skills add wittyreference/twilio-claude-plugin --skill context-hubgit clone --depth 1 https://github.com/wittyreference/twilio-claude-pluginWhat 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.00012 | $0.00765 |
| Opus 5 | $0.00006 | $0.00382 |
| Sonnet 5 | $0.00002 | $0.00153 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
context-hub 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 3d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: context-hub description: External API documentation fetcher. Use when writing code that calls external APIs (OpenAI, Stripe, etc.) to get curated docs and prevent hallucinated API shapes.
Context Hub — External API Documentation
Use context-hub (chub) to fetch curated, versioned API docs before writing code that calls external APIs. This prevents hallucinated API shapes and builds cross-session memory via annotations.
When to Use
- Before writing code that calls non-Twilio external APIs (Stripe, OpenAI, SendGrid, etc.)
- When unsure about current API parameters, response shapes, or SDK methods
- When the architect identifies external service dependencies
For Twilio APIs: Prefer the project's domain CLAUDE.md files and /twilio-docs skill — they are more comprehensive than context-hub's Twilio coverage. Use chub for Twilio only as a supplement.
Workflow
1. Search for docs
chub search "<api name>" # e.g., chub search "stripe"
chub search # list everything available
2. Fetch language-specific docs
chub get <id> --lang js # e.g., chub get stripe/api --lang js
chub get <id> --lang py # Python variant
3. Use the docs
Read the fetched content and use it to write correct code. Do not rely on memorized API shapes — use what the docs say.
4. Annotate what you learned
After completing the task, if you discovered a gotcha, workaround, or project-specific detail not in the doc, save it:
chub annotate <id> "Webhook verification requires raw body — do not parse before verifying"
Annotations persist locally across sessions and appear automatically on future chub get calls. Keep notes concise and actionable.
5. Give feedback
Rate the doc so authors can improve it. Ask the user before sending.
chub feedback <id> up # doc worked well
chub feedback <id> down --label outdated # doc needs updating
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.
- 3d ago First seen · 90 lines · 12 tokens per session scan A 505f194324f3
context-hub is a skill published in the GitHub repository wittyreference/twilio-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 765 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-31.
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…