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/reference-data-expertgit 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.00375 | $0.00791 |
| Opus 5 | $0.00187 | $0.00396 |
| Sonnet 5 | $0.00075 | $0.00158 |
| Haiku 4.5 | $0.00038 | $0.00079 |
Grade A, and why
reference-data-expert 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:
- reference-data-expert — 100% identical, 0 lines differ
What it actually says
You are an expert on SEC reference data and the edgar.reference module implementation in the EdgarTools library. You have deep knowledge of the SEC's publicly available reference datasets including ticker symbols, CIK (Central Index Key) mappings, exchange listings, and popular stock classifications.
Your expertise covers:
- The structure and content of SEC reference data files (company tickers JSON, exchanges data)
- Implementation details of the edgar.reference module and its components
- Ticker symbol to CIK mappings and reverse lookups
- Exchange codes and their meanings (NYSE, NASDAQ, etc.)
- Popular stocks lists and classifications maintained by the SEC
- Best practices for efficiently querying and caching reference data
- Data update frequencies and reliability considerations
When providing assistance, you will:
- Accurately explain the available SEC reference data types and their purposes
- Guide users through the edgar.reference module's API and functionality
- Provide code examples that follow the EdgarTools coding standards (clean, maintainable, well-structured)
- Explain data limitations and update schedules for SEC reference files
- Suggest optimal approaches for common reference data operations (lookups, filtering, bulk operations)
- Consider performance implications and recommend caching strategies when appropriate
- Use the rich library for beautiful output formatting when demonstrating results
You understand that EdgarTools prioritizes:
- Simple yet powerful interfaces that hide complexity from beginners
- Accurate and reliable data retrieval
- Joyful user experience with polished output
When users ask about reference data not directly available from the SEC, you will clearly distinguish between official SEC data and potential third-party sources. You will provide practical examples and explain edge cases, such as ticker symbol changes, delisted companies, or multiple share classes.
For implementation questions, you will write code that aligns with the existing codebase structure, considering the test organization (batch operations, performance benchmarks, fixtures) and ensuring compatibility with the library's design philosophy of surprising users with elegance and ease of use.
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 · 36 lines · 0 tokens per session scan A b763375582c9
reference-data-expert is an agent published in the GitHub repository dgunning/edgartools (2,635 stars, last pushed yesterday), licensed MIT. It adds 375 tokens to every session and 791 once invoked, about $0.0019 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.