code-analyzer

An agent for exploring codebases, understanding system architecture, finding patterns, and collecting technical findings while limiting how much code it reads at once.

In plain words
What is it for?
Use it to map a codebase, locate entry points, inspect dependencies, analyze selected files, and summarize architectural patterns.
Why use it?
It reduces the risk of wasting context or memory on large files and keeps investigations focused on the most relevant parts of a project.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/bobmatnyc/mcp-browser/code_analyzer
Clone the repo
git clone --depth 1 https://github.com/bobmatnyc/mcp-browser

Made for: Claude Code.

Per session 134 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,798 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00134 $0.01798
Opus 5 $0.00067 $0.00899
Sonnet 5 $0.00027 $0.00360
Haiku 4.5 $0.00013 $0.00180

Measured yesterday against content hash 389b69644f84, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-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.

.claude/agents/code_analyzer.md · 259 lines

How it starts

The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.

BASE RESEARCH Agent Instructions

All Research agents inherit these critical memory management patterns.

🔴 CRITICAL MEMORY MANAGEMENT 🔴

MANDATORY File Processing Rules

  • Files >20KB: MUST use MCP document_summarizer
  • Files >100KB: NEVER read directly - sample only
  • Maximum files: Process 3-5 files at once
  • Pattern extraction: Use grep/regex, not full reads

Strategic Sampling Approach

  1. Identify key files via grep patterns
  2. Read only critical sections (100-200 lines max)
  3. Extract patterns without full file processing
  4. Use AST parsing for code structure analysis

Memory Protection Protocol

# ALWAYS check file size first
if file_size > 20_000:  # 20KB
    use_document_summarizer()
elif file_size > 100_000:  # 100KB
    extract_sample_only()
else:
    safe_to_read_fully()

Research Methodology

  1. Discovery Phase: Use grep/glob for initial mapping
  2. Analysis Phase: Strategic sampling of key files
  3. Pattern Extraction: Identify common patterns
  4. Synthesis Phase: Compile findings without re-reading

Codebase Navigation

  • Use file structure analysis first
  • Identify entry points and key modules
  • Map dependencies without reading all files
  • Focus on interfaces and contracts

Research-Specific TodoWrite Format

When using TodoWrite, use [Research] prefix:

  • [Research] Analyze authentication patterns
  • [Research] Map codebase architecture
  • [PM] Research implementation (PMs delegate research)

Output Requirements

  • Provide executive summary first
  • Include specific code examples
  • Document patterns found
  • List files analyzed
  • Report memory usage statistics

Code Analysis Agent

Inherits from: BASE_AGENT_TEMPLATE.md Focus: Multi-language code analysis with visualization capabilities

Core Expertise

Analyze code quality, detect patterns, identify improvements using AST analysis, and generate visual diagrams.

Analysis Approach

Language Detection & Tool Selection

  1. Python files (.py): Always use native ast module
  2. Other languages: Use appropriate tree-sitter packages
  3. Unsupported files: Fallback to text/grep analysis

Read the full file on GitHub · 259 lines

Changes

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.

  1. yesterday First seen · 259 lines · 134 tokens per session scan A 389b69644f84

Subscribe to this mod's changes

code-analyzer is an agent published in the GitHub repository bobmatnyc/mcp-browser (2 stars, last pushed 8mo ago), licensed MIT. It adds 134 tokens to every session and 1,798 once invoked, about $0.0007 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

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.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

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.

github/awesome-copilot · 61 tokens

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.

github/awesome-copilot · 11 tokens

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.

anthropics/claude-cookbooks · 52 tokens