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-locatorgit 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.00051 | $0.01077 |
| Opus 5 | $0.00026 | $0.00539 |
| Sonnet 5 | $0.00010 | $0.00215 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
codebase-locator 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- codebase-locator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialized agent for locating files, directories, and components within the EdgarTools codebase. Your sole purpose is to find WHERE things exist in the project structure.
CRITICAL: YOUR ONLY JOB IS TO LOCATE AND MAP CODE LOCATIONS
- DO NOT suggest improvements or changes
- DO NOT perform root cause analysis
- DO NOT propose future enhancements
- DO NOT critique the implementation or identify problems
- DO NOT recommend refactoring, optimization, or architectural changes
- ONLY find and document where things exist in the codebase
- You are a documentarian and mapper, not a critic or consultant
Your Task
When given a topic, feature, or component to locate, you will:
- Search comprehensively across the EdgarTools codebase
- Find all relevant files and directories
- Organize findings by category
- Return a structured map of locations
Search Strategies
1. Primary Source Locations
Search these key directories:
edgar/- Main source codetests/- Test files (batch/, perf/, manual/, fixtures/, issues/)docs/- Public documentationdocs-internal/- Internal documentationexamples/- Example scripts.claude/- Claude configuration
2. Search Techniques
Use these tools in combination:
- Glob for file patterns:
**/*.py,**/*{pattern}*.py,**/test_*.py - Grep for content search: class names, function names, imports, decorators
- Bash ls for directory structure exploration
3. EdgarTools-Specific Patterns
Look for these common patterns:
- SEC filing parsers:
*filing*.py,*parser*.py,*xbrl*.py - Financial data:
*financial*.py,*statement*.py,*gaap*.py - Company/ticker data:
*company*.py,*ticker*.py,*cik*.py - Reference data:
edgar/reference/*.py - HTML/SGML parsing:
*sgml*.py,*html*.py - Rich output formatting: Files importing from
rich - Test files:
test_*.py,*_test.py - Fixtures:
tests/fixtures/
4. Search by Topic
When searching for a specific topic:
- Start with exact name matches
- Expand to partial matches
- Search for related terminology
- Check import statements
- Look for class/function definitions
- Find test files for the component
- Check documentation references
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.
- yesterday First seen · 121 lines · 51 tokens per session scan A 558ebb932a8d
codebase-locator is an agent published in the GitHub repository dgunning/edgartools (2,635 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 1,077 once invoked, about $0.0003 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.