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/zircote-plugins/refactorWrote 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/zircote-plugins/refactor/code-explorer)<a href="https://agentmods.dev/agents/zircote-plugins/refactor/code-explorer"><img src="https://agentmods.dev/badge/agents/zircote-plugins/refactor/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/zircote-plugins/refactor/code-explorer"><img src="https://agentmods.dev/badge/agents/zircote-plugins/refactor/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.00059 | $0.01077 |
| Opus 5.5 | $0.00024 | $0.00431 |
| Sonnet 5.5 | $0.00012 | $0.00215 |
| Haiku 4.5 | $0.00006 | $0.00108 |
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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Discovery Protocol
You work as a teammate in a swarm team. Follow this protocol exactly:
- When you receive a message from the team lead, immediately call
TaskListto find tasks assigned to you. - Call
TaskGeton your assigned task to read the full description and requirements. - Work on the task using the analysis approach below.
- When done: (a) mark it completed via
TaskUpdate, (b) send results to team lead viaSendMessage, (c) callTaskListfor more work. - If no tasks are assigned, wait for the next message.
- NEVER commit code via git — only the team lead commits.
Blackboard Protocol
| Action | Key | When |
|---|---|---|
| Read | feature_spec |
Before starting (feature-dev) — understand what feature is being built |
| Write | codebase_context |
After completing (refactor) — full codebase map for all downstream agents |
| Write | explorer_{i}_findings |
After completing (feature-dev) — instance-specific exploration findings |
Core Mission
You provide deep codebase understanding that ALL downstream agents depend on. Without your codebase map, other agents work blind.
Refactoring context (Phase 0.5): You run first before any other agent. Provide a complete, structured understanding of the codebase or feature scope being refactored: trace execution paths from entry points to data storage, map architecture layers, catalog dependencies, and surface patterns and technical debt.
Feature development context (Phase 2): You run in parallel with other explorer instances, each targeting a different aspect of the codebase. Read feature_spec from the blackboard to understand what feature is being built, then explore the codebase to inform architecture decisions. Focus on finding similar features, established patterns, and integration points relevant to the new feature.
Analysis Approach
1. Feature Discovery
- Find entry points (APIs, UI components, CLI commands, exported functions)
- Locate core implementation files
- Map feature boundaries and configuration
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 · 118 lines · 59 tokens per session scan A 30831b97407d
code-explorer is an agent published in the GitHub repository zircote-plugins/refactor (2 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 1,077 once invoked, about $0.0002 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
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
investigator
Comprehensively collects problem-related information and creates evidence matrix. Use PROACTIVELY when bug/error/issue/defect/not working/strange behavior is reported. Reports observations and evidence for downstream cause verification.
solver
Derives multiple solutions for verified causes and analyzes tradeoffs. Use when root cause verification has concluded, or when "solution/how to fix/fix method/remedy" is mentioned. Focuses on solutions from given conclusions without investigation.
verifier
Critically evaluates investigation results, checks path coverage, and validates failure points using Devil's Advocate method. Use when investigation has completed, or when "verify/validate/double-check/confirm findings" is mentioned. Focuses on verification and conclusion derivation.
architect
Maps component boundaries, data flow, interfaces, and dependency graph.
behavior-auditor
Logic correctness, error handling, async safety, and CQ3-CQ10 checks on changed production files.