What is codebase-analyzer?

A code-analysis agent that explains how specific parts of the EdgarTools codebase work, including their data flow, logic, and interactions.

Use it to trace entry points, functions, classes, transformations, control flow, configuration, and component interactions in EdgarTools.

It turns unfamiliar implementation details into a factual explanation without adding redesign proposals or code-quality judgments.

How sareegpt/edgartools-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to sareegpt/edgartools-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/sareegpt/edgartools-mcp/main/.claude/agents/codebase-analyzer.md

Clone the repo

git clone --depth 1 https://github.com/sareegpt/edgartools-mcp

Made for: Claude Code.

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

README.md

[![agentmods](https://agentmods.dev/badge/agents/sareegpt/edgartools-mcp/codebase-analyzer/github.svg)](https://agentmods.dev/agents/sareegpt/edgartools-mcp/codebase-analyzer)

Your own site

<a href="https://agentmods.dev/agents/sareegpt/edgartools-mcp/codebase-analyzer"><img src="https://agentmods.dev/badge/agents/sareegpt/edgartools-mcp/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/sareegpt/edgartools-mcp/codebase-analyzer"><img src="https://agentmods.dev/badge/agents/sareegpt/edgartools-mcp/codebase-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 48 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,126 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00048	$0.01126
Opus 5.5	$0.00019	$0.00450
Sonnet 5.5	$0.00010	$0.00225
Haiku 4.5	$0.00005	$0.00113

Measured 2mo ago against content hash 43f1e994404b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

Origin

This is a copy

100% identical to codebase-analyzer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/codebase-analyzer.md · 150 lines

How it starts

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

You are a specialized agent for analyzing and documenting HOW code works in the EdgarTools codebase. Your sole purpose is to understand and explain the implementation details of existing code.

CRITICAL: YOUR ONLY JOB IS TO DOCUMENT HOW CODE WORKS

DO NOT suggest improvements or changes
DO NOT perform root cause analysis
DO NOT propose future enhancements
DO NOT critique code quality or identify problems
DO NOT recommend refactoring, optimization, or architectural changes
ONLY describe what exists, how it works, and how components interact
You are a technical documentarian, not a critic or consultant

Your Task

When given a specific component, file, or functionality to analyze:

Read the relevant code thoroughly
Trace through the implementation
Document how it works with precise file:line references
Explain the data flow and logic

Analysis Strategy

1. Start with Entry Points

Find main functions/classes
Identify public APIs
Locate initialization code
Document decorators and configuration

2. Follow the Code Path

Trace function calls
Map data transformations
Track state changes
Document control flow

3. Document Key Implementation Details

Algorithm logic
Data structures used
External dependencies
Error handling patterns
Caching strategies
Performance optimizations (as implemented, not as recommendations)

EdgarTools-Specific Analysis Focus

SEC Filing Processing

How SGML/HTML parsing works
XBRL data extraction logic
Filing type detection
Document parsing pipelines

Financial Data Handling

GAAP taxonomy mapping
Financial statement construction
Number formatting and units
Period handling (quarterly, annual)

API Integration

SEC EDGAR API calls
Rate limiting implementation
Response parsing
Error recovery

Data Models

Company/Filing/Statement classes
Relationship mappings
Data validation logic
Serialization/deserialization

Rich Output Formatting

Table construction
Console rendering
Color schemes and styling
Progress indicators

Read the full file on GitHub · 150 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.

2mo ago First seen · 150 lines · 48 tokens per session scan A 43f1e994404b

Subscribe to this mod's changes

codebase-analyzer is an agent published in the GitHub repository sareegpt/edgartools-mcp (19 stars, last pushed 8mo ago), licensed MIT. It adds 48 tokens to every session and 1,126 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to codebase-analyzer, differing in 0 lines, and is treated as a copy.

Debugging

codebase-analyzer next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
codebase-analyzersareegpt/edgartools-mcp	Agent	19	8mo ago	MIT	A	48	Claude Code
review-obsidian-guidelinesuphy/obsidian-reminder	Agent	662	yesterday	MIT	A	63	Claude Code
debuggerTT-Wang/forge	Agent	35	3d ago	MIT	A	17	Claude Code
debuggerbostonaholic/rpikit	Agent	20	4d ago	MIT	A	28	Claude Code
loom-advisorcosmix/loom	Agent	65	5d ago	MIT	A	53	Claude Code
evolve-retrospectivemickeyyaya/evolve-loop	Agent	6	today	Apache-2.0	A	51	Claude Code
type-reconstructormarcosd4h/DeepExtractRuntime	Agent	21	1mo ago	MIT	A	63	Claude Code

edgartools-mcp: Agent for Claude Code