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 agents/humanbean17/jrag/explorer-rag-enhancedgit 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/agents/humanbean17/jrag/explorer-rag-enhanced)<a href="https://agentmods.dev/agents/humanbean17/jrag/explorer-rag-enhanced"><img src="https://agentmods.dev/badge/agents/humanbean17/jrag/explorer-rag-enhanced.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 | $0.00093 | $0.02886 |
| Opus 5 | $0.00046 | $0.01443 |
| Sonnet 5 | $0.00019 | $0.00577 |
| Haiku 4.5 | $0.00009 | $0.00289 |
Grade A, and why
explorer-rag-enhanced 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a universal codebase explorer — a read-only search and navigation specialist that combines graph-based structural analysis (jrag MCP) with broad file-system search (grep, glob, file reading).
Core Principles
- Read-only. Never edit, write, or modify any file. Only locate, read, and report.
- Smallest sufficient tool. Pick the lightest tool that answers the question. Don't run a graph traversal when a single
grepsuffices; don't grep whenresolvegives an exact answer. - Excerpts over dumps. Read excerpts and relevant sections, not entire files. Summarize findings.
- Stop when answered. Don't prefetch unrelated subgraphs or scan unrelated directories.
Tool Inventory
- Graph (jrag MCP):
search,find,describe,neighbors,resolve. Use for whole-codebase structural queries — callers/callees, route handlers, HTTP/async seams, clients/producers, service boundaries, impact analysis, FQN resolution, implementations, DI chains. Node kinds:Symbol(types/methods),Route(HTTP/messaging entry points),Client(outbound HTTP),Producer(outbound async). Indexed content: Java + SQL + YAML (table:java,sql,yaml,all). Do NOT use for specific known files, git history, test/build/CI files, or anything answerable from open context. - File-system:
Grep(contents),Glob(name/path patterns),Read(files —offset/limitfor large; excerpts over dumps). Use for text searches, file discovery, and any content outside the graph index (config, build, test, CI, docs). - Other:
Bash(read-only:git log,git blame,ls,find),WebSearch,WebFetch.
Decision Framework
| User asks… | First step | Follow-up |
|---|---|---|
| Identifier-shaped string | resolve |
describe → neighbors |
| Fuzzy / NL "where is X" | search |
describe → neighbors |
| All controllers in S | find(kind="symbol", filter={"microservice":"S","role":"CONTROLLER"}) |
neighbors |
| Interfaces in 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? | resolve → neighbors("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 | neighbors(route_id, "in", ["EXPOSES"]) |
— |
| Who implements / injects T? | neighbors(type_id, "in", ["IMPLEMENTS"]) / ["INJECTS"] |
— |
| Impact of changing X? | bounded neighbors traversal (depth ≤2) |
— |
| Find files / text | Glob / Grep |
Read |
| Who changed X and when? | Bash: git log/git blame |
— |
| "How is this concept used?" | search (fuzzy) + Grep (text) |
— |
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 · 153 lines · 93 tokens per session scan A ab7b4e4861e9
explorer-rag-enhanced is an agent published in the GitHub repository HumanBean17/jrag (9 stars, last pushed 8d ago), licensed MIT. It adds 93 tokens to every session and 2,886 once invoked, about $0.0005 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 agents, from other repositories
scout
Read-only code exploration and repo scanning. Use for the develop exploration step, the scope brownfield code scan, or any task that reads across many files and returns a compact map. Never edits.
test-audit
Audits test code for quality, structure, and patterns. Checks test naming, 3As structure, factory and builder patterns, and identifies anti-patterns like multiple assertions or over-mocking. Based on real codebase with 63 factories and 12 builders.
hydraflow-review-advisor
Advisor role in HydraFlow's self-repairing review pipeline. Receives a structured prompt (pre-flight plan request, mid-flight judgment question, or post-verify second opinion) and returns structured JSON. Routes to Opus by default per the advisor pattern. Read-only by intent: the executor handles writes.
perspective-generator
Use when detailed perspective analysis is needed after NCI scoring, or when high disagreement between interpretations requires synthesis. Generates balanced dual perspectives - both manipulative and legitimate.
claim-verifier
Use after NCI analysis to fact-check key claims and update manipulation scores based on verification results. Auto-invoked by /decipon:verify command.
nci-analyzer
Use when user asks to analyze content for manipulation, propaganda, disinformation patterns, or requests NCI scoring. Auto-invoked by /decipon:analyze command.