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.
git 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/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/agents/humanbean17/jrag/explorer-rag-enhanced"><img src="https://agentmods.dev/badge/agents/humanbean17/jrag/explorer-rag-enhanced.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.00093 | $0.02886 |
| Opus 5.5 | $0.00037 | $0.01154 |
| Sonnet 5.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 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 — 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.
- 1mo 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 29d ago), licensed MIT. It adds 93 tokens to every session and 2,886 once invoked, about $0.0004 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 agents, from other repositories
langchain4j-ai-development-expert
Provides expert LangChain4j development capability for building AI applications, RAG systems, ChatBots, and MCP servers. Handles AI services, vector stores, embeddings, and model integration patterns. Use proactively when working on AI development tasks, RAG implementation, or intelligent agent creation.
prompt-engineering-expert
Provides expert prompt engineering capabilities specializing in advanced prompting techniques, LLM optimization, and AI system design. Masters chain-of-thought, constitutional AI, and production prompt strategies. Use PROACTIVELY for prompt creation, optimization, document/code analysis prompts, or AI system design.…
langchain-specialist
Expert consultant for LangChain ecosystem development, LangSmith observability, LLM application architecture, and production deployment strategies. Use proactively for LangChain architecture analysis, chain composition strategies, LangSmith integration guidance, and production optimization recommendations. Provides…
data-engineer
Expert consultant for data pipeline design, ETL/ELT processes, data architecture, and data quality, providing analysis and recommendations without writing code. Use proactively for data infrastructure consultation, pipeline architecture guidance, stream processing strategy, data storage optimization, and data…
openai-api-specialist
Expert consultant for OpenAI API integration, model selection, cost optimization, and best practices. Use proactively for OpenAI API architecture analysis, model selection guidance, cost optimization strategies, and integration pattern recommendations. Provides consultation and recommendations only - does not write or…
unsloth-specialist
Expert consultant for Unsloth fine-tuning framework, memory optimization, training acceleration, and efficient model customization. Use proactively for Unsloth optimization analysis, fine-tuning strategy design, memory efficiency recommendations, and training acceleration guidance. Provides consultation and…