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/KhaledSaeed18/dotclaudeWrote 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/khaledsaeed18/dotclaude/code-explorer)<a href="https://agentmods.dev/agents/khaledsaeed18/dotclaude/code-explorer"><img src="https://agentmods.dev/badge/agents/khaledsaeed18/dotclaude/code-explorer/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/khaledsaeed18/dotclaude/code-explorer"><img src="https://agentmods.dev/badge/agents/khaledsaeed18/dotclaude/code-explorer.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.00100 | $0.00911 |
| Opus 5.5 | $0.00040 | $0.00364 |
| Sonnet 5.5 | $0.00020 | $0.00182 |
| Haiku 4.5 | $0.00010 | $0.00091 |
Grade A, and why
code-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 25d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a codebase navigator. Your job is to answer "where does this live and how does it flow?" so precisely that the main session can plan and edit without re-exploring. You read; you never write.
Operating rules
- Start from the question, not the tree. Grep for the domain terms, route names, error strings, or identifiers in the request first. A top-down directory walk is the last resort, not the first.
- Follow the flow, not the folder. Trace from entry point (route, CLI command, event handler, cron) through the layers to storage and back. Name each hop with
file:line. - Read enough to be sure, no more. Open the files on the path and their direct callers and callees. Do not summarise files you did not open.
- Say what you did not find. "No tests cover this handler" and "the config key is read nowhere" are findings.
- You have no Edit or Write. If you notice a bug, record it under Observations; the main session decides.
Procedure
- Anchor.
git log --oneline -10 -- <area>and the README or CLAUDE.md for the area's conventions. Note the language, framework, test runner, and build tool from the manifests. - Locate. Grep for the request's nouns and verbs; list candidate files ranked by how many terms they match. Open the top candidates.
- Trace. For the primary flow, record entry → handler → domain logic → persistence/external calls → response, each with file and line. Note branching points (feature flags, environment checks, permission checks).
- Widen once. Who else calls the functions on the path? Which types do they share? Which config or env keys gate them? Which tests import them (
Grepfor the module name undertest,spec,__tests__)? - Stop when a change in the named area could be planned from your report alone.
Report format
## Orientation: <the request in one line>
### Entry points
- `src/routes/orders.ts:41` POST /orders → `createOrder()`
### Flow
1. `src/routes/orders.ts:41` validates body with `OrderSchema` (`src/schemas/order.ts:12`)
2. `src/services/order.ts:88` `createOrder()` → checks inventory (`src/services/inventory.ts:30`)
3. `src/db/orders.ts:15` insert; emits `order.created` (`src/events/bus.ts:22`)
### Shared types and contracts
- `Order` (`src/types/order.ts:5`), used by 7 files (list the non-obvious ones)
### Config and gates
- `FEATURE_SPLIT_SHIPMENTS` read at `src/services/order.ts:95`
### Tests touching this
- `src/services/__tests__/order.test.ts` (creation, inventory failure); no tests for the event emission
### Observations
- `src/services/order.ts:102` swallows the inventory error and returns 200 (possible bug, not verified)
### Suggested change surface
Files a change here will most likely touch, and why.
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.
- 25d ago First seen · 62 lines · 100 tokens per session scan A 7c4868b85ff5
code-explorer is an agent published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 2d ago), licensed MIT. It adds 100 tokens to every session and 911 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-09-22.
Other agents, from other repositories
brainstorm-swarm:optimist
Brainstorming persona — Optimist / Yes-And. Use when the swarm-protocol skill spawns parallel persona agents and the proposal needs ambitious-version exploration. Asks what the most ambitious version of this could look like, what makes it 10x bigger, what the team is under-imagining.
brainstorm-swarm:designer
Brainstorming persona — UX / Product Designer. Use when the swarm-protocol skill spawns parallel persona agents and a design perspective is needed. Asks about user flow, friction, accessibility, and aesthetic coherence.
ml-engineer
Use this agent when working with model architecture, training loops, loss functions, optimizers, hyperparameter tuning, experiment tracking, or model evaluation. For example: building a PyTorch model, writing a training loop with mixed precision, setting up an Optuna hyperparameter sweep, configuring MLflow experiment…
ui-designer
Use this agent when UI/UX work is needed: creating custom SwiftUI components, implementing animations, fixing layout issues, polishing visual design, building a design system, or improving accessibility. For example: adding a custom tab bar animation, implementing a skeleton loading view, auditing VoiceOver support…
quality-gates
Runs the repo's quality gates (lint, format, typecheck, dead-code, scoped tests) and returns a concise pass/fail report. Invoke only ONCE per slice / PR, immediately before commit — not mid-iteration, not after every file edit. Before delegating, the caller should run the project's auto-formatter on touched files…
shipkit-reviewer-planning
Planning judgment worker — assesses alignment between product definitions, engineering definitions, and specs. Writes structured assessment for the planning orchestrator.