Borrowing it
Nothing to install: this file belongs to diillson/chatcli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/diillson/chatcli/main/.agent/agents/explorer-agent.mdgit clone --depth 1 https://github.com/diillson/chatcliWrote 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/diillson/chatcli/explorer-agent)<a href="https://agentmods.dev/agents/diillson/chatcli/explorer-agent"><img src="https://agentmods.dev/badge/agents/diillson/chatcli/explorer-agent/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/diillson/chatcli/explorer-agent"><img src="https://agentmods.dev/badge/agents/diillson/chatcli/explorer-agent.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.00040 | $0.00862 |
| Opus 5.5 | $0.00016 | $0.00345 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 74 lines · 40 tokens per session scan A 12c0e8249a15
explorer-agent is an agent published in the GitHub repository diillson/chatcli (93 stars, last pushed yesterday), licensed Apache-2.0. It adds 40 tokens to every session and 862 once invoked, about $0.0002 per session on Opus 5.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
fixer
Use for quick fixes, hotfixes, urgent patches, and time-sensitive bug repairs.
ebpf-kernel-engineer
Use this agent when working with eBPF kernel programs, system-level observability, or kernel programming tasks. Examples include: developing or modifying process.bpf.c and sslsniff.bpf.c programs, optimizing eBPF performance, debugging kernel compatibility issues, implementing new eBPF monitoring capabilities…
incident-responder
Handles production incidents with urgency and precision. Use IMMEDIATELY when production issues occur. Coordinates debugging, implements fixes, and documents post-mortems.
diagnosis-analyst
Use when a specific skill has recurring low grades, warning or critical status, regressions, or unclear failures after basic doctor/status review. Investigates logs, evals, audit history, and transcripts, then returns a root-cause report with exact next actions.
gsd-debug-session-manager
Manages multi-cycle /gsd:debug checkpoint and continuation loop in isolated context. Spawns gsd-debugger agents, handles checkpoints via AskUserQuestion, dispatches specialist skills, applies fixes. Returns compact summary to main context. Spawned by /gsd:debug command.
analytics_engineer_agent
An agent for deciding what app activity and system events should be recorded for analysis and troubleshooting. It covers user actions, errors, crashes, network failures, performance issues, and data-quality checks.