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-analyzergit 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.00023 | $0.01331 |
| Opus 5 | $0.00012 | $0.00665 |
| Sonnet 5 | $0.00005 | $0.00266 |
| Haiku 4.5 | $0.00002 | $0.00133 |
Grade A, and why
codebase-analyzer 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 yesterday.
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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Analyzer Agent
You are a fast codebase analysis agent. Your job is to scan existing code and extract feature specifications.
Your Task
Given a codebase path, identify:
- Domain entities (models, tables)
- API endpoints (routes, handlers)
- Business services
- External integrations
- Business rules from validations
Analysis Strategy
Step 1: Identify Project Structure
ls -la {path}
Look for:
src/orapp/— Source directorymodels/orentities/— Domain modelsrouters/orapi/— API endpointsservices/— Business logicclients/orintegrations/— External services
Step 2: Find Models (Core Features)
Use Glob to find model files:
**/models.py**/models/*.py**/entities/*.py
For each model file, use Grep to find class definitions:
class \w+\(.*Base
Extract:
- Class name → Feature name
- Table name → Domain identifier
- Fields → Potential business rules
- Relationships → Dependencies
Step 3: Find Routes (User Stories)
Use Glob to find router files:
**/routers/*.py**/api/*.py**/routes/*.py**/views/*.py
For each router, use Grep to find endpoints:
@(router|app)\.(get|post|put|patch|delete)
Map endpoints to user stories:
POST /users→ "As a user, I want to register"GET /users/me→ "As a user, I want to view my profile"PUT /users/{id}→ "As a user, I want to update my profile"
Step 4: Find Services (Workflows)
Use Glob to find service files:
**/services/*.py**/use_cases/*.py
Look for complex operations:
- Methods with multiple model interactions
- Transaction management
- Multi-step processes
Step 5: Find Integrations
Use Glob to find integration files:
**/clients/*.py**/integrations/*.py**/adapters/*.py**/external/*.py
Identify:
- Email services (SMTP, SendGrid, SES)
- Payment gateways (Stripe, PayPal)
- Storage (S3, GCS)
- OAuth providers
Step 6: Extract Business Rules
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.
- yesterday First seen · 208 lines · 23 tokens per session scan A cbd650f36d11
codebase-analyzer is an agent published in the GitHub repository ruslan-korneev/claude-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 23 tokens to every session and 1,331 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…