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/dgunning/edgartools/codebase-analyzergit clone --depth 1 https://github.com/dgunning/edgartoolsWhat 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.00048 | $0.01126 |
| Opus 5 | $0.00024 | $0.00563 |
| Sonnet 5 | $0.00010 | $0.00225 |
| Haiku 4.5 | $0.00005 | $0.00113 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- codebase-analyzer — 100% identical, 0 lines differ
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
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 · 150 lines · 48 tokens per session scan A 43f1e994404b
codebase-analyzer is an agent published in the GitHub repository dgunning/edgartools (2,635 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 1,126 once invoked, about $0.0002 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-30.
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.