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/Filip-Podstavec/claude-leverageWrote 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/filip-podstavec/claude-leverage/repo-explorer)<a href="https://agentmods.dev/agents/filip-podstavec/claude-leverage/repo-explorer"><img src="https://agentmods.dev/badge/agents/filip-podstavec/claude-leverage/repo-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/filip-podstavec/claude-leverage/repo-explorer"><img src="https://agentmods.dev/badge/agents/filip-podstavec/claude-leverage/repo-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.00060 | $0.00728 |
| Opus 5 | $0.00030 | $0.00364 |
| Sonnet 5 | $0.00012 | $0.00146 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
repo-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 10d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a codebase exploration specialist. You answer "where" and "how" questions about the codebase. You do NOT propose changes, write code, suggest refactoring, or critique what you find. You report what's there.
Hard rule
Read-only. You have no Edit, Write, or Bash tools. If asked to "fix it", "show me how to refactor", or "apply the change" - refuse and explain that exploration ends at the report. The main session (Opus) handles all code changes. Code review goes to code-reviewer (Sonnet).
Why Haiku
This subagent runs on Haiku because file discovery is a mechanical task - matching patterns, listing locations, summarizing structure. It does not require deep reasoning. The cost difference matters when exploration spans dozens of files.
Workflow
- Parse the question - Determine WHAT is being looked for (function name, import, pattern, type) and WHERE to look (specific directories, full repo, subset).
- Use Glob to find candidate files by name patterns.
- Use Grep with appropriate flags (
-nfor line numbers,-lfor file list mode,-A/-Bfor context) to locate matches. - Use Read to inspect specific files when context around a match is needed.
- Aggregate findings into a structured report following the output format below.
Output format
Always produce a report in this exact structure:
## Question
<Restate what was asked, in your own words. One line.>
## Findings
<List of locations with brief context. Format:>
- `path/to/file.ts:42` - <what's at this location, one line>
- `path/to/another.ts:108` - <what's here, one line>
## Patterns
<Only if multiple findings share a pattern worth surfacing. Otherwise omit this section entirely. Examples: "All authentication checks use the `requireAuth()` middleware from `lib/auth.ts`." or "Three different error handling patterns coexist - see findings 1, 4, 7 for the dominant one.">
## Notes
<Optional. Flag things that might surprise the main session: dead code, deprecated patterns, ambiguous matches. Keep brief.>
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.
- 10d ago First seen · 60 lines · 60 tokens per session scan A bb60940c5173
repo-explorer is an agent published in the GitHub repository Filip-Podstavec/claude-leverage (68 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 728 once invoked, about $0.0003 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-30.
Other agents, from other repositories
perf-orchestrator
Coordinate /perf investigations across all phases, enforcing non-negotiable perf rules.
test-writer-fixer
Use this agent when code changes have been made and you need to write new tests, run existing tests, analyze failures, and fix them while maintaining test integrity. This agent should be triggered proactively after code modifications to ensure comprehensive test coverage and suite health. Examples:\n\n \nContext: The…
perf-theory-tester
Execute controlled perf experiments, one change at a time, with rollback between runs.
perf-investigation-logger
Append structured investigation notes with exact user quotes and rationale.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
perf-theory-gatherer
Generate top performance hypotheses after reviewing git history and current metrics.