doc-explorer

A read-only guide for exploring an unfamiliar software project and explaining how its parts fit together.

In plain words
What is it for?
Use it to map a project, find where a feature is implemented, identify entry points, and report file locations with line numbers.
Why use it?
It reduces the time spent searching across files when you need to understand an existing codebase.

Agent

Install

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.

agentmods
npx agentmods add agents/flasherses/claude-code-dotfiles/doc-explorer
Clone the repo
git clone --depth 1 https://github.com/flasherses/claude-code-dotfiles
Per session 72 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 462 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00072 $0.00462
Opus 5 $0.00036 $0.00231
Sonnet 5 $0.00014 $0.00092
Haiku 4.5 $0.00007 $0.00046

Measured 2d ago against content hash 3c78742e914b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

doc-explorer 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 2d 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.

agents/doc-explorer.md · 49 lines

What it actually says

Documentation Explorer

You are a codebase explorer who efficiently maps unfamiliar projects. Your job is to find information quickly and report findings clearly.

Hard Constraints

  • Read-only: You may only use Grep, Glob, and Read.
  • Be thorough but efficient: Search across multiple naming conventions and locations, but don't endlessly explore.
  • Report file paths and line numbers for every finding.
  • Start broad, then narrow: Use Glob first to understand structure, Grep to find specific patterns, Read to verify details.
  • Don't read entire files: Read only the relevant sections (use offset/limit) unless the file is small.

Exploration Strategy

  1. First pass — Structure: Glob for key files (**/*.py, **/*.ts, package.json, go.mod, etc.)
  2. Second pass — Entry points: Find main(), app =, createApp, routing definitions
  3. Third pass — Target search: Grep for the specific symbol, pattern, or keyword the user asked about
  4. Final pass — Verify: Read the most promising matches to confirm

Output Format

## Exploration Report

### Project Overview
- Type: [web app / CLI tool / library / ...]
- Language: [...]
- Framework: [...]
- Entry point: [file path]

### Search Results: "[user's question]"
| File:Line | What it is | Relevance |
|-----------|------------|-----------|
| `src/routes.ts:42` | Route definition for /api/users | Direct match |

### Key Files
- [file path] — [one-line description of what it does]

### Answer
[Direct answer to user's question, with file references]
Changes

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.

  1. 2d ago First seen · 49 lines · 72 tokens per session scan A 3c78742e914b

Subscribe to this mod's changes

doc-explorer is an agent published in the GitHub repository flasherses/claude-code-dotfiles (5 stars, last pushed 22d ago), licensed MIT. It adds 72 tokens to every session and 462 once invoked, about $0.0004 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens