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 HumanBean17/jrag --skill explore-codebasegit clone --depth 1 https://github.com/HumanBean17/jragWrote 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/humanbean17/jrag/explore-codebase)<a href="https://agentmods.dev/skills/humanbean17/jrag/explore-codebase"><img src="https://agentmods.dev/badge/skills/humanbean17/jrag/explore-codebase/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/humanbean17/jrag/explore-codebase"><img src="https://agentmods.dev/badge/skills/humanbean17/jrag/explore-codebase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00117 | $0.03207 |
| Opus 5.5 | $0.00047 | $0.01283 |
| Sonnet 5.5 | $0.00023 | $0.00641 |
| Haiku 4.5 | $0.00012 | $0.00321 |
Grade A, and why
explore-codebase 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 1mo 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/explore-codebase — Universal codebase exploration
Read-only exploration combining jrag graph navigation with broad file-system search.
Use any time you must search, locate, navigate, or explore. Do NOT use when the answer is already in context or for a single known file — read it directly.
Core Principles
- Read-only. Never edit, write, or modify any file.
- Smallest sufficient tool. Pick the lightest tool that answers the question.
- Stop when answered. Don't prefetch unrelated subgraphs or directories.
Tool Inventory
- Graph (jrag MCP):
search,find,describe,neighbors,resolve. Node kinds:Symbol(types/methods),Route(HTTP/messaging entry points),Client(outbound HTTP),Producer(outbound async). Indexed content: JVM sources (.java/.kt) only — SQL/YAML/config are not indexed; grep and read them directly. - File-system:
Grep(content/regex),Glob(name/path patterns),Read(offset/limitfor large files). - Other:
Bash(read-only:git log,git blame,ls,find),WebSearch/WebFetch.
Decision Framework
| User asks… | First step | Follow-up |
|---|---|---|
| Identifier-shaped string | resolve (+ optional hint_kind) |
describe → neighbors |
| Fuzzy / NL "where is X" | search |
describe → neighbors |
| All controllers in service S | find(kind="symbol", filter={"microservice":"S","role":"CONTROLLER"}) |
neighbors CALLS/EXPOSES |
| Interfaces in service S | find(..., filter={"microservice":"S","symbol_kind":"interface"}) |
neighbors/describe |
| HTTP / messaging entry points | find(kind="route", filter={…}) |
describe |
| Outbound HTTP clients | find(kind="client", filter={…}) |
neighbors(..., "out", ["HTTP_CALLS"]) |
| Outbound async producers | find(kind="producer", filter={…}) |
neighbors(..., "out", ["ASYNC_CALLS"]) |
| Who calls method M? | id via resolve/find/search |
neighbors(ids, "in", ["CALLS"]) |
| What does M call? | same | neighbors(ids, "out", ["CALLS"]) |
| Who hits this route? | route id | neighbors(ids, "in", ["HTTP_CALLS","ASYNC_CALLS","EXPOSES"]) |
| Handler for route | route id | neighbors(ids, "in", ["EXPOSES"]) |
| Who implements/injects T? | type symbol id | neighbors(ids, "in", ["IMPLEMENTS"]) or ["INJECTS"] |
| Impact of changing X? | bounded neighbors in loop (CALLS, INJECTS, …) |
Grep fallback |
| Find files / text | Glob / Grep |
Read |
| Who changed X and when? | Bash: git log/git blame |
— |
| "How is this configured?" | Glob + Grep (config files are not indexed) |
Read sections |
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.
- 1mo ago Changed db3bd071fe21
- 1mo ago First seen · 166 lines · 117 tokens per session scan A b83cf57880c4
explore-codebase is a skill published in the GitHub repository HumanBean17/jrag (9 stars, last pushed 22d ago), licensed MIT. It adds 117 tokens to every session and 3,207 once invoked, about $0.0005 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
sync
Run /sync as the last step after a change is complete, around merge, to keep durable knowledge current. Updates root and nested AGENTS.md, reconciles the scope from repo evidence, and flags specs the change made stale. Surgical edits only: it adds lines, and rewrites single lines it owns. Never a whole section, never…
debug
Run /debug to find and fix a bug's root cause: a test failing for an unclear reason, /check verify finding a failure, or behavior being wrong. Runs a reproduce, localize, hypothesize, test, fix, verify loop, makes the minimal fix, and hands a regression test to /test. No features, no extra refactors.
architect
Run /architect when choosing between approaches, designing a feature or page, picking a tech stack, or when /develop says a decision is owed, anytime a load bearing technical decision is unmade. Asks deep questions, recommends an answer, and writes a build spec to docs/specs/. Owns all spec files.
scope
Run /scope to turn a product idea into a living, coarse scope in docs/scope/ and keep it current: plan a new product, plan the next slice, enroll one named feature, or run with no argument to reconcile after shipping and queue what is next. Seeds WHAT to build; /architect designs, /develop builds.
headless
Assists in the creation of a headless Claude Code batch script that runs an isolated micro-session per item (file, line, task) for ad-hoc automation such as bulk migrations, lint-fix loops, or doc generation.
coordination-audit
Produce a structured organizational diagnostic that quantifies time spent on specification vs coordination vs execution, saved as a persistent audit artifact to $HOME/.ai-first-kit/. Conducts a guided 5-question interview, classifies every workflow structure by actual function, and identifies highest-ROI automation…