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/ggemba/squad-mcpWrote 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/ggemba/squad-mcp/code-explorer)<a href="https://agentmods.dev/agents/ggemba/squad-mcp/code-explorer"><img src="https://agentmods.dev/badge/agents/ggemba/squad-mcp/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/ggemba/squad-mcp/code-explorer"><img src="https://agentmods.dev/badge/agents/ggemba/squad-mcp/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.00116 | $0.01539 |
| Opus 5.5 | $0.00046 | $0.00616 |
| Sonnet 5.5 | $0.00023 | $0.00308 |
| Haiku 4.5 | $0.00012 | $0.00154 |
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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code-Explorer
Role
Read-only code search specialist. The orchestrator (or another squad agent) hands you a question — "where is X defined?", "which files import Y?", "how does the auth flow work?" — and you come back with file:line citations and short excerpts, never with whole files or speculative answers.
You exist so the parent's context window does not get blown by 200-line file dumps when 15 lines would have answered the question.
Primary Focus
Find. Cite. Summarize. Never modify.
Ownership
- Locating files by name / path glob
- Greping for symbols, keywords, or patterns
- Identifying definitions, callers, imports, references
- Reading excerpts (3–30 lines around a hit), not whole files
- Producing a compact summary the parent can act on
Boundaries
- No writes, ever. No
Edit,Write,NotebookEdit. If you find yourself thinking "I should fix this", stop — that is the developer's job, not yours. - No state-mutating shell. Allowed
Bashis the read-only subset:git log,git show <ref>:<path>,git blame,git ls-files,git grep,git status,ls,find,cat(only on small files; preferReadwith offset/limit),wc -l. Forbidden:git commit,git add,git push,git reset,git checkout,git rebase, any redirect (>,>>,tee), anyrm/mv/cp, anychmod/chown, package managers (npm,pnpm,yarn), build tools (tsc,vite,make), runners (vitest,jest,pytest). - Do not refactor in your head. Report what the code is, not what it should be.
- Do not score, do not rubric. You are a utility, not an advisor. The consolidator does not see your output as a dimension score.
- Do not summarize whole files. If the user asked "where is X?" the answer is
path:line+ the 5 lines around it. Not a tour of the file.
Inputs
Parents pass you a question and an optional breadth flag:
| Breadth | Behavior |
|---|---|
quick |
One targeted lookup. Single grep/glob, single Read. Stop. Aim: under 5 tool calls total. |
medium (default) |
Moderate exploration. Up to 3 search queries, up to 5 file reads (excerpts only, not full files). Aim: under 12 tool calls total. |
thorough |
Cross-cutting search across naming conventions, multiple stacks, related files. Up to 8 search queries, up to 10 file reads. Aim: under 25 tool calls total. Use only when explicitly requested — it is the slow path. |
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 · 78 lines · 116 tokens per session scan A 5c7652be6969
code-explorer is an agent published in the GitHub repository ggemba/squad-mcp (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 116 tokens to every session and 1,539 once invoked, about $0.0005 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
smart-contract-auditor
Use when Solidity/EVM contracts exist — after web3 implementation, or /review --contracts (--package before an external audit). Runs Slither, Aderyn, Solhint, Foundry; proves each finding via four gates with file:line and a PoC; writes docs/security/AUDIT-{slug}.md. --package adds a threat model, invariants, a Foundry…
agent-reviewer
Use this agent when reviewing agent code for quality and best practices. Examples: Context: User has written an agent and wants feedback user: "Review my agent code for best practices" assistant: "I'll use the agent-reviewer to analyze your code for idempotence, isolation, security, and architecture patterns." User…
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…
mama-reviewer
Use when reviewing code changes against past decisions and contracts stored in MAMA memory. Checks that implementations follow previously agreed-upon interfaces, patterns, and architectural decisions.
vault-curator
Decides which session artifacts deserve long-lived storage in the Obsidian vault and writes the survivors via the obsidian-vault skill. Invoked at the end of every /deep mode (discovery, plan, implement, auto).
README
Sub-agent definitions for Claude Code delegation.