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/theagenticguy/opencodehub/codehub-exploringnpx skills add theagenticguy/opencodehub --skill codehub-exploringgit clone --depth 1 https://github.com/theagenticguy/opencodehubWhat 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.00063 | $0.01305 |
| Opus 5 | $0.00032 | $0.00652 |
| Sonnet 5 | $0.00013 | $0.00261 |
| Haiku 4.5 | $0.00006 | $0.00130 |
Grade A, and why
codehub-exploring 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.
This is a copy
94% identical to opencodehub-exploring — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploring Codebases with OpenCodeHub
When to Use
- "How does authentication work?"
- "What's the project structure?"
- "Where is the database logic?"
- "Show me the request lifecycle."
- Onboarding to a codebase you have not seen before.
Workflow
1. mcp__codehub__list_repos → Pick the repo name
2. READ codehub://repo/{name}/context → Stats + staleness envelope
3. mcp__codehub__query({query: "<concept>", repo}) → Hybrid BM25 + vector hits, grouped by process
4. mcp__codehub__context({name: "<symbol>", repo}) → 360-degree view, categorised edges, cochange side-section
5. mcp__codehub__sql for process traces → Step ordering from the relations table
6. Read source files only after the graph has pointed you at the hot spots
If the context envelope warns the index is stale, run
codehub analyzein the terminal first.
Checklist
- [ ] mcp__codehub__list_repos — confirm the repo
- [ ] READ codehub://repo/{name}/context — check freshness
- [ ] mcp__codehub__query for the concept
- [ ] Scan returned processes (execution flows) before scanning files
- [ ] mcp__codehub__context on the strongest hit
- [ ] Inspect confidenceBreakdown — prefer confirmed edges for architectural claims
- [ ] Review cochanges as a secondary signal (git history, NOT call deps)
- [ ] Follow PROCESS_STEP edges via mcp__codehub__sql to trace the flow end-to-end
- [ ] Read source files for implementation detail only
Tools
mcp__codehub__query — hybrid BM25 + vector search, grouped by process
mcp__codehub__query({ query: "payment processing", repo: "my-app", limit: 20 })
→ results: ranked symbols with file path, kind, score
→ processes: execution flows that contain the top hits (populated when PROCESS_STEP edges exist)
→ next_steps: pointer to the next tool
Use it as the first broad read after the context resource. Prefer it over Grep for concept-level questions.
mcp__codehub__context — 360-degree view of a symbol
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 · 121 lines · 63 tokens per session scan A 62d0109fca9f
codehub-exploring is a skill published in the GitHub repository theagenticguy/opencodehub (3 stars, last pushed 21d ago), licensed Apache-2.0. It adds 63 tokens to every session and 1,305 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to opencodehub-exploring, differing in 14 lines, and is treated as a copy.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.