agentmods.dev

edgartools: Agent for Claude Code

.claude/agents/issue-handler.md

issue-handler is an agent for Claude Code from dgunning/edgartools. It costs 0 tokens per session (3,405 once invoked), scanned A, original, MIT.

An expert agent for handling GitHub issues in EdgarTools, a Python library for working with U.S. Securities and Exchange Commission filings. It focuses on financial data, filing access, XBRL parsing, performance, and compatibility problems.

In plain words
What is it for?
Investigating and resolving issues involving SEC filings, XBRL financial statements, downloads and attachments, company facts, slow operations, memory use, dependencies, and operating systems.
Why use it?
It brings the project’s filing and financial-data context into issue triage, reproduction, and resolution instead of treating each report as a generic bug.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is dgunning/edgartools's own configuration. It tells Claude Code how to work on edgartools itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything edgartools configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python tools/quick_debug.py --empty-periods ACCESSION_NUMBER # For cash flow issues.

not rated 2.8krepo +6 yesterday A scan 0 tokens original MIT
View source ↗ dgunning/edgartools edgartools.readthedocs.io
About the project

EdgarTools is a Python library that turns SEC EDGAR filings into structured, typed data, including financial statements, insider trades, fund holdings, and other filing types. It is used to analyze regulatory filings in notebooks, data pipelines, and AI systems. Its catalogue add-ons operate the library through skills, commands, instructions, and an MCP server.

dgunning/edgartools · 2,837 stars · on GitHub · edgartools.readthedocs.io

Reuse

Borrowing it

Nothing to install: this file belongs to dgunning/edgartools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dgunning/edgartools/main/.claude/agents/issue-handler.md
Clone the repo
git clone --depth 1 https://github.com/dgunning/edgartools

Made for: Claude Code.

Wrote 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.

agentmods badge for issue-handler

README.md
[![agentmods](https://agentmods.dev/badge/agents/dgunning/edgartools/issue-handler/github.svg)](https://agentmods.dev/agents/dgunning/edgartools/issue-handler)
Your own site
<a href="https://agentmods.dev/agents/dgunning/edgartools/issue-handler"><img src="https://agentmods.dev/badge/agents/dgunning/edgartools/issue-handler/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for issue-handler

Your own site · 80×15
<a href="https://agentmods.dev/agents/dgunning/edgartools/issue-handler"><img src="https://agentmods.dev/badge/agents/dgunning/edgartools/issue-handler.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,405 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.03405
Opus 5.5 $0.00000 $0.01362
Sonnet 5.5 $0.00000 $0.00681
Haiku 4.5 $0.00000 $0.00341

Measured 2mo ago against content hash d2d7d8fc9d60, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

issue-handler 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 2mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/agents/issue-handler.md · 321 lines

How it starts

The opening of the file, as written. The whole thing — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an expert GitHub issue handler specializing in the EdgarTools project - a Python library for SEC Edgar filings. You have comprehensive expertise in financial data processing, XBRL parsing, SEC filing formats, and the common issues that arise when working with complex financial datasets.

Your Core Expertise:

  1. SEC Filings Domain Knowledge:

    • XBRL statement parsing and concept mapping challenges
    • Financial data validation and accuracy verification
    • Filing download and attachment handling issues
    • Company facts API integration problems
    • Performance optimization for large financial datasets
    • Cross-platform compatibility with Windows/macOS/Linux

  2. Issue Pattern Recognition:

    • Data Quality Issues: Incorrect financial values, missing data, calculation errors
    • XBRL Parsing Issues: Statement rendering problems, concept mapping failures, period mismatches
    • Filing Access Issues: Download failures, attachment problems, authentication issues
    • Performance Issues: Slow operations, memory leaks, inefficient queries
    • Compatibility Issues: Platform-specific bugs, dependency conflicts, version mismatches

  3. EdgarTools Architecture:

    • Core library structure (edgar/ packages and modules)
    • Test infrastructure (1000+ tests in tests/, tests/perf/, with scripts in scripts/batch/, scripts/manual/)
    • Data processing pipelines for financial statements
    • Caching strategies and performance optimizations
    • Integration patterns with pandas, pyarrow, and rich libraries

Your Systematic Workflow:

Phase 1: Issue Triage & Analysis

  1. Fetch issue details using gh api repos/dgunning/edgartools/issues/{number}
  2. Create Beads issue: bd create --external-ref 'gh:{number}' --title "Issue title" --status open --labels triage
  3. Analyze error messages, stack traces, and reproduction steps
  4. Categorize issue type (data-quality, xbrl-parsing, filing-access, performance, compatibility)
  5. Assess scope: single company vs. systemic, recent vs. long-standing
  6. Assess initial severity (critical vs normal) - see Phase 1.5 for criteria
  7. Update Beads: bd update ISSUE_ID --labels {category} to track categorization

Phase 1.5: Product Manager Coordination (REQUIRED FOR BUGS)

CRITICAL: For bug reports, you MUST coordinate with product-manager before implementing fixes. This ensures proper severity classification and release planning.

When to Coordinate with PM

Coordinate for:

  • ✅ Bug reports (data issues, parsing failures, functionality broken)
  • ✅ Regressions (something that worked before is now broken)
  • ✅ Security vulnerabilities
  • ✅ Performance degradations

Skip coordination for (proceed directly):

  • Documentation typos
  • Test improvements
  • Code comment updates
  • Formatting fixes

Read the full file on GitHub · 321 lines

Changes

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.

  1. 2mo ago First seen · 321 lines · 0 tokens per session scan A d2d7d8fc9d60

Subscribe to this mod's changes

issue-handler is an agent published in the GitHub repository dgunning/edgartools (2,837 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,405 tokens. 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.

10-k10-qDebuggingbalance-sheetedgarfilingsfinancials
Related

issue-handler compared with agents from other repositories

issue-handler next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
issue-handlerdgunning/edgartoolsAgent2.8kyesterdayMITA0Claude Code
review-obsidian-guidelinesuphy/obsidian-reminderAgent662yesterdayMITA63Claude Code
debuggerTT-Wang/forgeAgent353d agoMITA17Claude Code
debuggerbostonaholic/rpikitAgent204d agoMITA28Claude Code
loom-advisorcosmix/loomAgent655d agoMITA53Claude Code
evolve-retrospectivemickeyyaya/evolve-loopAgent6todayApache-2.0A51Claude Code
type-reconstructormarcosd4h/DeepExtractRuntimeAgent211mo agoMITA63Claude Code