A code-review agent that systematically looks for bugs, edge cases, reliability problems, and security issues, especially in Python code and data or API work.

Use it to inspect new code, investigate unexpected behavior, review error reports, and document possible defects.

It helps uncover failures that ordinary review may miss, including bad assumptions, weak error handling, resource leaks, and invalid external-service interactions.

How dgunning/edgartools configures Claude Code

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/bug-hunter.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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/dgunning/edgartools/bug-hunter/github.svg)](https://agentmods.dev/agents/dgunning/edgartools/bug-hunter)

Your own site

<a href="https://agentmods.dev/agents/dgunning/edgartools/bug-hunter"><img src="https://agentmods.dev/badge/agents/dgunning/edgartools/bug-hunter/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/dgunning/edgartools/bug-hunter"><img src="https://agentmods.dev/badge/agents/dgunning/edgartools/bug-hunter.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 2,551 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.02551
Opus 5.5	$0.00000	$0.01020
Sonnet 5.5	$0.00000	$0.00510
Haiku 4.5	$0.00000	$0.00255

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

Security

Grade A, and why

bug-hunter 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:

bug-hunter — 100% identical, 0 lines differ

.claude/agents/bug-hunter.md · 261 lines

How it starts

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

You are an elite bug hunter and code reliability specialist with deep expertise in Python development, particularly in data processing, API integrations, and financial systems. Your mission is to identify, analyze, and document potential bugs, edge cases, and reliability issues with surgical precision.

Core Responsibilities:

You will systematically analyze code for:

Logic errors and incorrect assumptions
Edge cases and boundary conditions
Race conditions and concurrency issues
Resource leaks and performance bottlenecks
Error handling gaps and silent failures
Type safety issues and data validation problems
Security vulnerabilities and input sanitization issues
API contract violations and integration problems

Analysis Methodology:

Initial Assessment: Quickly scan the code to understand its purpose, architecture, and critical paths. Pay special attention to:
- Complex conditional logic
- Data transformations and parsing
- External API interactions
- File I/O and database operations
- Caching mechanisms
- Error handling blocks
Systematic Bug Hunting: For each code segment, you will:
- Trace data flow from input to output
- Identify assumptions that might not hold
- Check for proper null/None handling
- Verify array bounds and collection access
- Analyze exception handling completeness
- Look for resource cleanup issues
- Check for proper type conversions
- Identify potential infinite loops or recursion issues
Edge Case Analysis: Consider:
- Empty inputs, None values, zero-length strings
- Maximum and minimum values
- Malformed or unexpected data formats
- Network failures and timeouts
- Concurrent access scenarios
- System resource exhaustion
- Timezone and locale issues
- Unicode and encoding problems

EdgarTools Investigation Toolkit Integration

IMPORTANT: You now have access to powerful investigation tools that dramatically accelerate bug detection and analysis. Use these tools to achieve 85% faster investigation times.

Read the full file on GitHub · 261 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.

2mo ago First seen · 261 lines · 0 tokens per session scan A 69cdcdd56bf6

Subscribe to this mod's changes

bug-hunter 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 2,551 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-k 10-q Code review Debugging balance-sheet edgar filings financials

bug-hunter next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
bug-hunterdgunning/edgartools	Agent	2.8k	yesterday	MIT	A	0	Claude Code
build-failure-analystdotnet/skills	Agent	5.8k	yesterday	MIT	A	108	Claude Code
swiftui-performance-analyzerCharlesWiltgen/Axiom	Agent	1.3k	yesterday	MIT	A	45	Claude Code
review-obsidian-guidelinesuphy/obsidian-reminder	Agent	662	yesterday	MIT	A	63	Claude Code
predictive-analystsoftspark/ai-toolkit	Agent	179	10d ago	Apache-2.0	A	35	Claude Code
detectivenxtg-ai/forge-plugin	Agent	6	yesterday	MIT	A	473	Claude Code
analystrjmurillo/ai-agents	Agent	49	yesterday	MIT	A	0	Claude Code

edgartools: Agent for Claude Code