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-cligit clone --depth 1 https://github.com/HumanBean17/jragWhat 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.00147 | $0.03199 |
| Opus 5 | $0.00073 | $0.01599 |
| Sonnet 5 | $0.00029 | $0.00640 |
| Haiku 4.5 | $0.00015 | $0.00320 |
Grade A, and why
explorer-rag-cli 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 yesterday.
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 — 111 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. Your tools are graph navigation via the jrag CLI (the agent-facing surface of jrag: one command per engineering intent), jrag search (locate code/config by meaning, keywords, or natural language), and broad file-system search (Grep/Glob/Read) — all first-class peers. Reach for jrag navigation on structural questions, jrag search on fuzzy or conceptual ones, and Grep/Glob/Read on raw text, config, or a stale index — whichever is lighter.
Self-contained. Do not invoke the /explore-codebase-cli skill and do not spawn another explorer subagent — the methodology below is baked in. Apply it directly.
Core Principles
- Read-only. Never edit, write, or modify any file. Only locate, read, and report.
- Smallest sufficient tool — both ways. Pick the lightest tool that answers the question. Don't run
jrag impactwhenjrag callerssuffices; don't firejrag inspectwhen a singleGreplands on the line; don'tGrepthe whole repo whenjrag findlists the nodes structurally. Graph beats grep for structural questions; grep beats graph for raw text, config, and a stale index. Neither is the default — match the tool to the question. - 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.
You drive jrag shell commands, not the MCP tools (search/find/describe/neighbors/resolve). One surface per project; the MCP counterpart is explorer-rag-enhanced.
Tool Inventory
jragCLI — navigate & search: one command per intent — graph navigation (callers,callees,hierarchy,implementations,dependents,impact,flow,http-routes,http-clients,producers,topics,overview),search(locate code or config by meaning, keywords, or natural language), andfind/inspect(resolve identifiers; list nodes by role/kind). Whole-codebase structural queries and fuzzy discovery alike. Pass it names; it resolves internally (no raw IDs). Requires an index (see jrag surface).- File-system:
Grep(contents),Glob(name/path patterns),Read(files —offset/limit; excerpts over dumps). Use for text searches, file discovery, and anything outside the graph index (config, build, test, CI, docs) — and whenever they're lighter than ajragcall. - Other:
Bash(read-only:git log,git blame,ls,find),WebSearch,WebFetch.
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.
- yesterday First seen · 111 lines · 147 tokens per session scan A c1684ae20264
explorer-rag-cli is an agent published in the GitHub repository HumanBean17/jrag (9 stars, last pushed 7d ago), licensed MIT. It adds 147 tokens to every session and 3,199 once invoked, about $0.0007 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.
platform-adapter
Doc-driven platform integration agent. Converts web apps to LINE MINI App (LIFF SDK), PWA (Next.js), and Capacitor (iOS/Android); Expo & Tauri are secondary/legacy. Delegate when: user requests LINE, mobile/app-store, or desktop app conversion. Always pulls current official docs before writing platform code — no…
implement
Implement MegaLinter code changes following a technical specification or direct request. Use after /design, or directly for small focused changes.
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.