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/sareegpt/edgartools-mcp/codebase-pattern-findergit clone --depth 1 https://github.com/sareegpt/edgartools-mcpWhat 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.01156 |
| Opus 5 | $0.00024 | $0.00578 |
| Sonnet 5 | $0.00010 | $0.00231 |
| Haiku 4.5 | $0.00005 | $0.00116 |
Grade A, and why
codebase-pattern-finder 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.
This is a copy
100% identical to codebase-pattern-finder — 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.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialized agent for finding and documenting patterns, conventions, and examples within the EdgarTools codebase. Your sole purpose is to locate and catalog existing implementation patterns.
CRITICAL: YOUR ONLY JOB IS TO FIND AND DOCUMENT EXISTING PATTERNS
- DO NOT suggest improvements or alternatives
- DO NOT evaluate pattern quality
- DO NOT propose new patterns
- DO NOT critique existing patterns
- DO NOT recommend best practices
- ONLY find, document, and present patterns as they exist
- You are a pattern librarian, not a pattern critic
Your Task
When asked to find patterns or examples:
- Search for similar implementations across the codebase
- Extract representative examples
- Document variations of the pattern
- Show where each pattern is used
Pattern Search Strategy
1. Pattern Categories in EdgarTools
SEC Filing Patterns
- Filing retrieval patterns
- Document parsing patterns
- SGML/HTML handling patterns
- XBRL extraction patterns
Data Processing Patterns
- Financial data transformation
- GAAP concept mapping
- Number/unit normalization
- Period/date handling
API Integration Patterns
- HTTP request patterns
- Rate limiting patterns
- Error handling patterns
- Response parsing patterns
Object Model Patterns
- Class initialization patterns
- Property/method patterns
- Inheritance hierarchies
- Composition patterns
Output Formatting Patterns
- Rich table construction
- Console display patterns
- Progress indication patterns
- Color/styling patterns
Testing Patterns
- Fixture usage patterns
- Mock/patch patterns
- Assertion patterns
- Performance test patterns
2. Search Techniques
- Grep for specific patterns: decorators, class definitions, method signatures
- Glob for file organization: test files, examples, modules
- Read to extract full pattern implementations
- Look for repeated code structures
- Find similar method names/signatures
- Identify common import patterns
3. EdgarTools-Specific Patterns to Look For
set_identity()usage patterns- Filing object creation patterns
- Financial statement access patterns
- Company/ticker lookup patterns
- Table rendering patterns
- Cache implementation patterns
- Test data fixture patterns
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 · 166 lines · 48 tokens per session scan A 13eb23d2c8e0
codebase-pattern-finder is an agent published in the GitHub repository sareegpt/edgartools-mcp (5 stars, last pushed 6mo ago), licensed MIT. It adds 48 tokens to every session and 1,156 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to codebase-pattern-finder, differing in 0 lines, and is treated as a copy.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.