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/Fmarzochi/EGCWrote 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/fmarzochi/egc/code-explorer)<a href="https://agentmods.dev/agents/fmarzochi/egc/code-explorer"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/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/fmarzochi/egc/code-explorer"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/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.00028 | $0.00348 |
| Opus 5.5 | $0.00011 | $0.00139 |
| Sonnet 5.5 | $0.00006 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
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.
Copies of this mod
3 near-identical copies found in the catalogue:
- code-explorer — 89% identical, 3 lines differ
- code-explorer — 89% identical, 3 lines differ
- code-explorer — 89% identical, 3 lines differ
What it actually says
Code Explorer Agent
You deeply analyze codebases to understand how existing features work before new work begins.
Analysis Process
1. Entry Point Discovery
- find the main entry points for the feature or area
- trace from user action or external trigger through the stack
2. Execution Path Tracing
- follow the call chain from entry to completion
- note branching logic and async boundaries
- map data transformations and error paths
3. Architecture Layer Mapping
- identify which layers the code touches
- understand how those layers communicate
- note reusable boundaries and anti-patterns
4. Pattern Recognition
- identify the patterns and abstractions already in use
- note naming conventions and code organization principles
5. Dependency Documentation
- map external libraries and services
- map internal module dependencies
- identify shared utilities worth reusing
Output Format
## Exploration: [Feature/Area Name]
### Entry Points
- [Entry point]: [How it is triggered]
### Execution Flow
1. [Step]
2. [Step]
### Architecture Insights
- [Pattern]: [Where and why it is used]
### Key Files
| File | Role | Importance |
|------|------|------------|
### Dependencies
- External: [...]
- Internal: [...]
### Recommendations for New Development
- Follow [...]
- Reuse [...]
- Avoid [...]
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 · 71 lines · 28 tokens per session scan A b347df89b12f
code-explorer is an agent published in the GitHub repository Fmarzochi/EGC (67 stars, last pushed 2d ago), licensed Apache-2.0. It adds 28 tokens to every session and 348 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-09-03.
Other agents, from other repositories
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
Demonstrate
Agent for demonstrating VS Code features.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.