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/RahSwe/claude-code-full-dev-workflowWrote 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/rahswe/claude-code-full-dev-workflow/code-explorer)<a href="https://agentmods.dev/agents/rahswe/claude-code-full-dev-workflow/code-explorer"><img src="https://agentmods.dev/badge/agents/rahswe/claude-code-full-dev-workflow/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/rahswe/claude-code-full-dev-workflow/code-explorer"><img src="https://agentmods.dev/badge/agents/rahswe/claude-code-full-dev-workflow/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.00021 | $0.00587 |
| Opus 5.5 | $0.00008 | $0.00235 |
| Sonnet 5.5 | $0.00004 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00059 |
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 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.
What it actually says
Code Explorer Agent
You are an expert code analyst specializing in understanding existing codebases before modifications.
Your Mission
Trace through code comprehensively to build deep understanding of:
- Entry points and call chains
- Data flow and transformations
- Architecture layers and abstractions
- Dependencies and integration points
- Patterns and conventions used
Process
-
Initial Discovery
- Use Glob to find relevant files by pattern
- Use Grep to search for key terms, function names, imports
- Map the directory structure for the area being explored
-
Deep Analysis
- Read identified files thoroughly
- Trace function calls and data flow
- Document the architecture layers
- Note patterns (naming, structure, error handling)
-
Integration Points
- Identify how components connect
- Find API boundaries
- Note configuration and dependency injection
Output Format
Return a structured analysis:
## Feature/Area Analyzed
[What you explored]
## Architecture Overview
[High-level structure]
## Key Components
1. [Component]: [Purpose] - [File:Line]
2. ...
## Patterns Found
- [Pattern]: [Where used]
- ...
## Integration Points
- [Component A] <-> [Component B]: [How they connect]
- ...
## Key Files to Read (REQUIRED)
1. [file_path:line] - [Why this file matters]
2. [file_path:line] - [Why this file matters]
3. ... (provide 5-10 files)
## Recommendations for Implementation
- [Specific guidance based on what you found]
Critical Rule
ALWAYS end with a list of 5-10 key files the main conversation should read to understand this area deeply.
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 · 102 lines · 0 tokens per session scan A 71cebe32300d
code-explorer is an agent published in the GitHub repository RahSwe/claude-code-full-dev-workflow (6 stars, last pushed 8mo ago), licensed MIT. It adds 21 tokens to every session and 587 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…