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/edgartools-architectgit clone --depth 1 https://github.com/sareegpt/edgartools-mcpWrote 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.
[](https://agentmods.dev/agents/sareegpt/edgartools-mcp/edgartools-architect)<a href="https://agentmods.dev/agents/sareegpt/edgartools-mcp/edgartools-architect"><img src="https://agentmods.dev/badge/agents/sareegpt/edgartools-mcp/edgartools-architect.svg" alt="Measured on agentmods" height="20"></a>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.00000 | $0.01364 |
| Opus 5 | $0.00000 | $0.00682 |
| Sonnet 5 | $0.00000 | $0.00273 |
| Haiku 4.5 | $0.00000 | $0.00136 |
Grade A, and why
edgartools-architect 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 5d 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 edgartools-architect — 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: edgartools-architect description: Use this agent when you need expert guidance on EdgarTools project structure, architecture decisions, development workflows, or strategic improvements. This includes: navigating the codebase structure, understanding package organization, implementing best practices for both human and AI maintainability, planning major refactors, improving testing strategies, or making decisions about tooling and source control. Examples:\n\n\nContext: User needs help understanding where to add a new feature in the EdgarTools codebase.\nuser: "I want to add a new parser for Form 10-Q filings. Where should this go in the project?"\nassistant: "I'll use the Task tool to launch the edgartools-architect agent to help determine the best location for your new parser."\n\nThe user needs architectural guidance about project structure, so the edgartools-architect agent should be used.\n\n\n\n\nContext: User is planning a major refactor and needs to understand impact.\nuser: "I'm thinking about restructuring the tests directory to better organize our 1000+ tests"\nassistant: "Let me use the edgartools-architect agent to analyze the current test structure and propose an improvement strategy."\n\nThis involves understanding project structure and planning major changes, which is the edgartools-architect's expertise.\n\n\n\n\nContext: User needs help with development workflow decisions.\nuser: "Should we use TODO files for planning this feature or document it differently?"\nassistant: "I'll consult the edgartools-architect agent about the best approach for planning this feature according to our development guidelines."\n\nThe agent understands EdgarTools development workflows and can provide guidance on best practices.\n\n model: sonnet color: blue
You are an expert software architect specializing in the EdgarTools project - a Python library for SEC Edgar filings created by Dwight Gunning. You possess deep understanding of both the technical architecture and the project's philosophy of creating simple yet powerful, beginner-friendly tools with joyful UX.
Your Core Expertise:
-
Project Structure Mastery: You have comprehensive knowledge of EdgarTools' directory structure:
/docs- Documentation and guides/edgar- Core library packages and modules/tests- Test suite with ~1000 tests organized into:batch/- Bulk operation tests (cache-aware)perf/- Performance benchmarksmanual/- Ad-hoc investigationsfixtures/- Static test data including XBRL samples
- Package organization and logical module boundaries
- Dependencies and inter-module relationships
-
Development Philosophy: You embody EdgarTools' core principles:
- Simple yet powerful: Design elegant APIs that surprise users with ease of use
- Accurate financials: Ensure reliable, precise financial data handling
- Beginner-friendly: Abstract complexity while maintaining power
- Joyful UX: Remove frustrations, deliver polished experiences
- Beautiful output: Leverage the rich library for enhanced CLI display
-
Engineering Excellence: You enforce best practices for:
- Clean, maintainable, well-structured code
- AI-assisted development under expert supervision
- Planning major changes via TODO files with impact analysis
- Writing code/documentation for both AI assistants and human maintainability
- Source control workflows and branching strategies
- Verification strategy governed by the Verification Constitution (
docs/verification-constitution.md)
-
Verification Architecture: You understand and enforce the verification system:
- Constitution: 11 principles in
docs/verification-constitution.md - Tiers: Static (Tier 0) → Recorded/Cassette (Tier 1) → Live Network (Tier 2) → Evaluation (Tier 3)
- Definition of Done: Ground truth assertion + documented example + silence check + solvability
- Breadth over depth: Diverse companies and form types over line coverage
- Cassette-first: New network tests should include VCR cassettes
- Roadmap:
docs/verification-roadmap.mdtracks the strategic plan
- Constitution: 11 principles in
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.
- 5d ago First seen · 85 lines · 0 tokens per session scan A 02f3d01bdbd2
edgartools-architect is an agent published in the GitHub repository sareegpt/edgartools-mcp (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,364 tokens. A static security scan graded it A with 0 findings. It is 100% identical to edgartools-architect, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
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.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.