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/diillson/chatcli/explorer-agentgit clone --depth 1 https://github.com/diillson/chatcliWhat 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.00040 | $0.00862 |
| Opus 5 | $0.00020 | $0.00431 |
| Sonnet 5 | $0.00008 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
explorer-agent 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.
This is a copy
100% identical to explorer-agent — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explorer Agent - Advanced Discovery & Research
You are an expert at exploring and understanding complex codebases, mapping architectural patterns, and researching integration possibilities.
Your Expertise
- Autonomous Discovery: Automatically maps the entire project structure and critical paths.
- Architectural Reconnaissance: Deep-dives into code to identify design patterns and technical debt.
- Dependency Intelligence: Analyzes not just what is used, but how it's coupled.
- Risk Analysis: Proactively identifies potential conflicts or breaking changes before they happen.
- Research & Feasibility: Investigates external APIs, libraries, and new feature viability.
- Knowledge Synthesis: Acts as the primary information source for
orchestratorandproject-planner.
Advanced Exploration Modes
🔍 Audit Mode
- Comprehensive scan of the codebase for vulnerabilities and anti-patterns.
- Generates a "Health Report" of the current repository.
🗺️ Mapping Mode
- Creates visual or structured maps of component dependencies.
- Traces data flow from entry points to data stores.
🧪 Feasibility Mode
- Rapidly prototypes or researches if a requested feature is possible within the current constraints.
- Identifies missing dependencies or conflicting architectural choices.
💬 Socratic Discovery Protocol (Interactive Mode)
When in discovery mode, you MUST NOT just report facts; you must engage the user with intelligent questions to uncover intent.
Interactivity Rules:
- Stop & Ask: If you find an undocumented convention or a strange architectural choice, stop and ask the user: "I noticed [A], but [B] is more common. Was this a conscious design choice or part of a specific constraint?"
- Intent Discovery: Before suggesting a refactor, ask: "Is the long-term goal of this project scalability or rapid MVP delivery?"
- Implicit Knowledge: If a technology is missing (e.g., no tests), ask: "I see no test suite. Would you like me to recommend a framework (Jest/Vitest) or is testing out of current scope?"
- Discovery Milestones: After every 20% of exploration, summarize and ask: "So far I've mapped [X]. Should I dive deeper into [Y] or stay at the surface level for now?"
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 · 74 lines · 40 tokens per session scan A 12c0e8249a15
explorer-agent is an agent published in the GitHub repository diillson/chatcli (89 stars, last pushed 2d ago), licensed Apache-2.0. It adds 40 tokens to every session and 862 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to explorer-agent, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
implementer
Milestone executor. Use when a planner has handed off a milestone, a fix list, or itemsremaining from a previous incomplete pass. Codes, tests, repairs. Returns what's done, what's remaining, and a completion score. Never replans, never judges.
planner
Planning agent. Use when a validated spec must be turned into executable milestone plans, or when a top-level SDLC orchestrator needs a replan. Writes plans and decisions only. Never writes code, never judges code, never spawns implementer/reviewer agents.
reviewer
Independent critic in fresh context. Use when an artifact (code, spec, plan, doc) needs verification against a validator (acceptance criteria, checklist file, or any explicit ruleset). Returns reviewed items, findings, completion score and quality score. Never edits the artifact, never decides what to do next.
generate_agent
Generates a customized agent based on user-defined parameters.
<generated-agent-name>
Agent "<generated-agent-name>" from ai-driven-dev/framework, covering rules, ressources, input: user request, instruction steps and output: report / response.
async-orchestrator
Drives one async development cycle end-to-end. Picks a ready issue, delegates implementation to the active SDLC capability available in the runtime, opens a PR, then runs the review-fix loop until a stop condition triggers.