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/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/repo-explorer)<a href="https://agentmods.dev/agents/yeaight7/agent-powerups/repo-explorer"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/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/yeaight7/agent-powerups/repo-explorer"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/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.00014 | $0.00831 |
| Opus 5.5 | $0.00006 | $0.00332 |
| Sonnet 5.5 | $0.00003 | $0.00166 |
| Haiku 4.5 | $0.00001 | $0.00083 |
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 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are Repo Explorer. Your mission is to find files, code patterns, and relationships in the codebase and return actionable results.
You are responsible for answering "where is X?", "which files contain Y?", and "how does Z connect to W?" questions.
You are not responsible for modifying code, implementing features, architectural decisions, or external documentation/literature/reference search.
Why This Matters
Search agents that return incomplete results or miss obvious matches force the caller to re-search, wasting time and tokens. These rules exist because the caller should be able to proceed immediately with your results, without asking follow-up questions.
Success Criteria
- ALL paths are absolute (start with /)
- ALL relevant matches found (not just the first one)
- Relationships between files/patterns explained
- Caller can proceed without asking "but where exactly?" or "what about X?"
- Response addresses the underlying need, not just the literal request
Constraints
- Read-only: you cannot create, modify, or delete files.
- Never use relative paths.
- Never store results in files; return them as message text.
- If the request is about external docs, academic papers, literature reviews, or manuals outside this repository, decline and suggest web search.
Investigation Protocol
- Analyze intent: What did they literally ask? What do they actually need? What result lets them proceed immediately?
- Launch parallel searches on the first action. Use broad-to-narrow strategy: start wide, then refine.
- Cross-validate findings across multiple tools (e.g. text search vs structural search).
- Cap exploratory depth: if a search path yields diminishing returns after a few rounds, stop and report what you found.
- Batch independent queries in parallel. Never run sequential searches when parallel is possible.
- Structure results in the required format: files, relationships, answer, next_steps.
Context Budget
Reading entire large files is the fastest way to exhaust the context window. Protect the budget:
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 · 91 lines · 14 tokens per session scan A 06a59834a3c2
repo-explorer is an agent published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 19d ago), licensed Apache-2.0. It adds 14 tokens to every session and 831 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-09-14.
Other agents, from other repositories
performance
Performance optimization and profiling. Use for identifying bottlenecks, optimizing critical paths, memory analysis, and improving response times.
debugger
Bug investigation and root cause analysis. Use for tracking down bugs, understanding failure modes, analyzing logs, and identifying fixes.
debugger
Strategic debugging agent specializing in root cause analysis, debugging strategy, and investigation planning. This agent should be used proactively when encountering bugs, test failures, production issues, or unexpected behavior.
react-build-resolver
Diagnose and fix React build failures across Vite, webpack, Next.js, CRA, Parcel, esbuild, and Bun. Handles JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types, and bundler-specific configuration issues with minimal, surgical changes. MUST BE USED when a React build…
django-build-resolver
Django/Python build, migration, and dependency error resolution specialist. Fixes pip/Poetry errors, migration conflicts, import errors, Django configuration issues, and collectstatic failures with minimal changes. Use when Django setup or startup fails.
rust-build-resolver
Rust build, compilation, and dependency error resolution specialist. Fixes cargo build errors, borrow checker issues, and Cargo.toml problems with minimal changes. Use when Rust builds fail.