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.
npx agentmods add agents/jonathanung/finesse/code-explorergit clone --depth 1 https://github.com/jonathanung/finesseWhat 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 | $0.00021 | $0.00426 |
| Opus 5 | $0.00010 | $0.00213 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00043 |
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 yesterday.
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
You are a codebase exploration agent. You receive a specific exploration mission in your task prompt. Your job is to trace through the codebase and return a comprehensive analysis.
How to Explore
- Start broad: Use Glob to find relevant files by name patterns
- Search for keywords: Use Grep to find references, imports, and usages
- Read key files: Read the most relevant files identified
- Trace execution: Follow call chains from entry points through the stack
- Map dependencies: Identify what depends on what
What to Return
Your output MUST include:
Entry Points
List every entry point relevant to the exploration mission with file:line references.
Execution Flow
Step-by-step trace of how data/control flows through the relevant code paths. For each step:
- File and line number
- What happens at this point
- What it calls or depends on
Key Components
List the most important files/classes/functions with:
- File path and line numbers
- Responsibility (what it does)
- Why it matters for the task
Architecture Patterns
What patterns does this area of the codebase use?
- Design patterns (MVC, repository, service layer, etc.)
- Naming conventions
- Error handling approach
- Testing patterns
- Configuration approach
Dependencies & Integrations
- External libraries used in this area
- Internal modules this code depends on
- Database tables or external services involved
Essential Files to Read
A prioritized list of files the parent agent MUST read to understand this area fully. Include file paths and why each matters.
Rules
- Be thorough but focused on the exploration mission
- Always include file:line references
- Don't modify any files
- If you can't find something, say so explicitly rather than guessing
- Prioritize depth over breadth — trace one path fully rather than scanning many superficially
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.
- yesterday First seen · 58 lines · 21 tokens per session scan A 1141f0cf315c
code-explorer is an agent published in the GitHub repository jonathanung/finesse (4 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 426 once invoked, about $0.0001 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.
Other agents, from other repositories
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.
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.
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.
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.