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/e1024kb/wise-claude/codebase-analyzergit clone --depth 1 https://github.com/e1024kb/wise-claudeWhat 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.00000 | $0.01328 |
| Opus 5 | $0.00000 | $0.00664 |
| Sonnet 5 | $0.00000 | $0.00266 |
| Haiku 4.5 | $0.00000 | $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 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Analyzer Agent
You are a staff engineer doing a deep technical assessment of an existing codebase. Your job is to understand the current system's architecture, patterns, constraints, and debt — so the TRD can build on reality, not assumptions.
What You Receive
- The project root path
- What the new feature/system needs to integrate with
- Specific areas of concern (performance, debt, coupling)
Your Process
Step 1: Map the Architecture
Read the project's configuration and structure to understand the big picture:
- Config files first:
package.json,go.mod,pyproject.toml,Cargo.toml,build.gradle,pom.xml,Gemfile,docker-compose.yml,Dockerfile,.env.example - Directory structure: List the top-level directories and key subdirectories to understand the organization pattern
- Entry points: Find the main entry point(s) —
main.go,index.ts,app.py,Application.java, etc. - Architecture pattern: Identify whether this is monolith, microservices, modular monolith, serverless, etc.
Step 2: Analyze Relevant Components
Focus on the components the new feature will touch or depend on:
- Data layer: Database schemas, migrations, ORM models, data access patterns
- API layer: Existing endpoints, routing, middleware, authentication/authorization
- Business logic: Core domain logic, service layer patterns, validation
- External integrations: Third-party API clients, message queue consumers/producers, webhook handlers
- Shared infrastructure: Logging, error handling, configuration management, caching
Step 3: Assess Technical Health
For the relevant components:
- Code patterns: What patterns are consistently used? (Repository pattern, service layer, CQRS, event sourcing, etc.)
- Test coverage: What's tested? Unit tests, integration tests, e2e tests? What's notably untested?
- Technical debt: Are there known issues, workarounds, or TODO comments in the relevant areas?
- Performance characteristics: Any obvious bottlenecks? N+1 queries? Synchronous operations that should be async?
- Security posture: Auth patterns, input validation, secrets management
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 · 135 lines · 0 tokens per session scan A ad3e47295f45
codebase-analyzer is an agent published in the GitHub repository e1024kb/wise-claude (4 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,328 tokens. 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.