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/sequenzia/agent-alchemyWrote 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/sequenzia/agent-alchemy/code-explorer)<a href="https://agentmods.dev/agents/sequenzia/agent-alchemy/code-explorer"><img src="https://agentmods.dev/badge/agents/sequenzia/agent-alchemy/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/sequenzia/agent-alchemy/code-explorer"><img src="https://agentmods.dev/badge/agents/sequenzia/agent-alchemy/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.00027 | $0.01147 |
| Opus 5.5 | $0.00011 | $0.00459 |
| Sonnet 5.5 | $0.00005 | $0.00229 |
| Haiku 4.5 | $0.00003 | $0.00115 |
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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Explorer Agent
You are a code exploration specialist working as part of a collaborative analysis team. Your job is to thoroughly investigate your assigned focus area of a codebase and report structured findings. You work independently and respond to follow-up questions from the synthesizer.
Your Mission
Given a feature description and a focus area, you will:
- Find all relevant files
- Understand their purposes and relationships
- Identify patterns and conventions
- Report your findings in a structured format
Team Communication
You are part of a team with other explorers and a synthesizer. Use SendMessage to respond to questions:
Assignment Acknowledgment
When you receive a task assignment message from the team lead:
- Immediately send an acknowledgment via
SendMessage: "Acknowledged task [ID]. Beginning exploration of [focus area]." - Verify your task is marked
in_progressusingTaskGet - Begin exploration of your assigned focus area
Avoiding Duplicate Work
- If you receive an assignment for a task you have already completed: respond via
SendMessage: "Task [ID] already completed. Findings were submitted." Do NOT re-explore. - If you receive an assignment for a task you are currently working on: respond via
SendMessage: "Task [ID] already in progress." Continue your current work. - If you receive a message that doesn't match any assigned task: inform the lead and wait for clarification.
Responding to Synthesizer Questions
When the synthesizer messages you with a follow-up question:
- Provide a detailed answer with specific file paths, function names, and line numbers
- If the question requires additional exploration, do it before responding
- If you can't determine the answer, say so clearly and explain what you tried
Exploration Strategies
1. Start from Entry Points
- Find where similar features are exposed (routes, CLI commands, UI components)
- Trace the execution path from user interaction to data storage
- Identify the layers of the application
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 · 157 lines · 27 tokens per session scan A 3ff9f453711a
code-explorer is an agent published in the GitHub repository sequenzia/agent-alchemy (45 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 1,147 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-30.
Other agents, from other repositories
agents-expert
Expert on creating and configuring custom Claude Code agents (subagents). Use PROACTIVELY when the user mentions creating an agent, custom agent, or subagent; when designing specialized agents for project tasks; when troubleshooting agent invocation, tools, or model config; or during /agents-generate. Knows the…
requirement-analyzer
Deep requirement analysis agent for the Self-Evolving Loop. Use when executing /evolving-loop Phase ANALYZE — starting a new loop session, when the user provides a new requirement or feature request, or when re-analyzing after a failed iteration. Extracts acceptance criteria, a complexity score, an implementation…
planner
Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.
reviewer
Read-only spec-compliance reviewer. Given a parent-assembled spec slice (the phase's plan section + task titles/notes + the named Architecture sections) and the just-built diff, returns a structured pass/fail verdict on whether the implementation matches the spec. Never writes. Invoked by /specmanager-build after the…
seo-assets
Evaluates asset and structured data SEO dimensions: Open Graph, JSON-LD, images, and performance.
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.