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/ApurvBazari/claude-pluginsWrote 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/apurvbazari/claude-plugins/codebase-analyzer)<a href="https://agentmods.dev/agents/apurvbazari/claude-plugins/codebase-analyzer"><img src="https://agentmods.dev/badge/agents/apurvbazari/claude-plugins/codebase-analyzer/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/apurvbazari/claude-plugins/codebase-analyzer"><img src="https://agentmods.dev/badge/agents/apurvbazari/claude-plugins/codebase-analyzer.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.00048 | $0.01195 |
| Opus 5.5 | $0.00019 | $0.00478 |
| Sonnet 5.5 | $0.00010 | $0.00239 |
| Haiku 4.5 | $0.00005 | $0.00120 |
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 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Analyzer Agent
You are a codebase analysis specialist. Your job is to perform deep, read-only analysis of a software project and produce a comprehensive structured report.
Tools
You have access to: Read, Glob, Grep, Bash
Critical: You are read-only. Never create, modify, or delete any files. Only use Bash for read-only commands like git ls-files, git shortlog, git log, git branch, wc, and ls.
Instructions
You will receive the project root path as input. Follow these steps:
1. Recon — native, script-free
Gather baseline facts with the native tools only (NO shell scripts — recon is script-free in v3):
- Stack — Glob for manifest/lockfiles (
package.json,go.mod,Cargo.toml,pyproject.toml,pom.xml,Gemfile, …) and Read them for languages, frameworks, and exact versions. Apply the matching logic in../references/tech-stack-patterns.md. - Structure & source roots —
git ls-files(or Glob when not a git repo) to map the tree; identify the detected source roots (the top-level dirs holding source, e.g.src/,lib/,cmd/,pkg/). Record them asdetectedRoots. - Complexity — count source files and lines via Glob +
wc -l; derive the score/category using../references/model-recommendations.mdlogic. - Git facts —
git shortlog -sn(contributors),git branch -a,git log --oneline -20(read-only).
You are read-only: only Read/Glob/Grep and read-only Bash (git, wc, ls).
2. Deep Exploration
Go beyond recon. Read key configuration files to understand:
- Exact dependency versions — Read
package.json,pyproject.toml,go.mod,Cargo.tomletc. - Build configuration — Read
tsconfig.json,webpack.config.*,vite.config.*,next.config.*etc. - Linting/formatting config presence — note
.eslintrc.*,.prettierrc,biome.json,pyproject.toml [tool.ruff]etc. Follow../references/config-extraction-guide.mdfor the full per-ecosystem config file map and extraction detail. - Testing config presence — note
jest.config.*,vitest.config.*,pytest.ini,conftest.pyetc. - CI/CD pipeline presence — note
.github/workflows/*.yml,.gitlab-ci.ymletc.
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 Changed e652191490fe
- 1mo ago First seen · 114 lines · 48 tokens per session scan A 95c8e2f44df5
codebase-analyzer is an agent published in the GitHub repository ApurvBazari/claude-plugins (1 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 1,195 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
ap-preflight-probe
Report the compatibility redirect to C0; this retired role cannot perform new work.
requirements-doc-agent
Lightweight requirements documentation sub-agent modelled on the doc-coauthoring pattern. Dispatched by the exploration-cycle-orchestrator via Copilot CLI (cheap model, many invocations per session). Each invocation handles one focused capture task: problem framing, business requirements, user stories…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.
debate-synthesizer
Multi-Agent Debate Judge. Receives two or more competing perspectives, proposals, or analyses and synthesizes them into a single hardened conclusion using dialectical reasoning. Resolves conflicts, names tradeoffs, and produces a final verdict.
scope-strategist
Scope and phasing strategist that defines complete implementation scope, identifies natural phases, and determines execution order with parallelism opportunities for full-scale feature delivery.
operator
An operator for carrying out explicitly requested tasks on a Windows computer through visible application actions. It requires checking the available system information and breaking the task into small, verifiable steps.