Borrowing it
Nothing to install: this file belongs to theagenticguy/opencodehub. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/theagenticguy/opencodehub/main/.claude/skills/opencodehub-exploring/SKILL.mdgit clone --depth 1 https://github.com/theagenticguy/opencodehubWrote 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/theagenticguy/opencodehub/opencodehub-exploring)<a href="https://agentmods.dev/skills/theagenticguy/opencodehub/opencodehub-exploring"><img src="https://agentmods.dev/badge/skills/theagenticguy/opencodehub/opencodehub-exploring/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/theagenticguy/opencodehub/opencodehub-exploring"><img src="https://agentmods.dev/badge/skills/theagenticguy/opencodehub/opencodehub-exploring.svg" alt="Reviewed on agentmods" width="80" 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.00064 | $0.01306 |
| Opus 5.5 | $0.00026 | $0.00522 |
| Sonnet 5.5 | $0.00013 | $0.00261 |
| Haiku 4.5 | $0.00006 | $0.00131 |
Grade A, and why
opencodehub-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 2mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- codehub-exploring — 94% identical, 14 lines differ
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.
- 2mo ago First seen · 121 lines · 64 tokens per session scan A e4951bd167db
opencodehub-exploring is a skill published in the GitHub repository theagenticguy/opencodehub (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 64 tokens to every session and 1,306 once invoked, about $0.0003 per session on Opus 5.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 debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…