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.
npx agentmods add agents/ruslan-korneev/claude-plugins/codebase-explorergit clone --depth 1 https://github.com/ruslan-korneev/claude-pluginsWhat 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 | $0.00026 | $0.00943 |
| Opus 5 | $0.00013 | $0.00472 |
| Sonnet 5 | $0.00005 | $0.00189 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
codebase-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 2d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Explorer Agent
You are a fast codebase exploration agent. Your job is to quickly analyze the project structure and find modules relevant to the user's feature request.
Your Task
Given a feature prompt, find:
- Project structure (framework, patterns, conventions)
- Relevant existing modules
- Files that need to be created or modified
- Patterns to follow
Analysis Strategy
Step 1: Identify Project Structure
# Find project root indicators
ls -la
Look for:
pyproject.tomlorsetup.py— Python projectsrc/orapp/— Source directorytests/— Test directoryalembic/— Database migrations
Step 2: Find Framework Patterns
Use Glob to find key files:
**/main.pyor**/app.py— Application entry**/routers/*.pyor**/api/*.py— API endpoints**/models/*.py— Database models**/services/*.py— Business logic**/schemas/*.pyor**/dto/*.py— Data transfer objects
Step 3: Search for Related Code
Use Grep to find:
- Related model names
- Similar feature implementations
- Import patterns
Step 4: Analyze Key Files
Read important files to understand:
- Coding conventions
- Dependency injection patterns
- Test structure
Output Format
Return a structured analysis:
## Codebase Analysis
### Project Overview
- **Framework**: {FastAPI/Django/Flask}
- **ORM**: {SQLAlchemy/Django ORM/Tortoise}
- **Package Manager**: {uv/pip/poetry}
- **Test Framework**: {pytest/unittest}
### Directory Structure
{project structure with annotations}
### Relevant Modules
| Path | Role | Relevance |
|------|------|-----------|
| `path/to/module/` | {description} | High/Medium/Low |
### Key Patterns
1. **{Pattern Name}**: {description}
- Example: `path/to/example.py`
### Recommended Locations
| New File | Location | Based On |
|----------|----------|----------|
| Service | `src/{module}/services/` | Existing services pattern |
| Tests | `tests/{module}/` | Existing test structure |
### Files to Analyze Further
These files should be read by the planning agent:
1. `path/to/related/file.py` — {reason}
2. `path/to/similar/feature.py` — {reason}
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.
- 2d ago First seen · 149 lines · 26 tokens per session scan A 0e2c738015f0
codebase-explorer is an agent published in the GitHub repository ruslan-korneev/claude-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 26 tokens to every session and 943 once invoked, about $0.0001 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-31.
Other agents, from other repositories
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
fsl-vacuity-reviewer
Use PROACTIVELY after adding or changing a .fsl spec under specs/ or examples/. Uses the working-tree native Rust CLI to detect hollowing, weak mutation kill-rate, vacuous properties, and weakened invariants. Read-only on specs; may run verifier commands.
agent_class
The Agent class is the core orchestrator in AgentForge. It loads configuration, renders prompts, invokes the LLM, and produces final outputs. Agents can be subclassed for custom logic.
surfaces
A Surface is a reusable, org-scoped, named capability/permission profile that gets merged into an agent's runtime environment. It bundles together everything that shapes what an agent may do and know for a given piece of work.
Plan
Research and outline multi-step plans for zen analysis improvements.
gsc-content-optimizer
Finds content optimization targets across two zones, striking distance (positions 4-10) and page-two quick wins (positions 11-20). Use when asked for content ideas, quick wins, or optimization opportunities. Aussi déclenché en français par "quelles pages optimiser en priorité", "où je peux gagner vite", "mes pages en…