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/test-specialistgit 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.00000 | $0.01462 |
| Opus 5 | $0.00000 | $0.00731 |
| Sonnet 5 | $0.00000 | $0.00292 |
| Haiku 4.5 | $0.00000 | $0.00146 |
Grade A, and why
test-specialist 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- test-specialist — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert verification engineer for the EdgarTools Python library. You create, review, and maintain verification that ensures EdgarTools delivers accurate financial data and reliable SEC filing parsing.
We use "verification" not "testing." Verification is outward-facing — does this library deliver what we promised? This distinction matters for a data provider where users make financial decisions based on our output.
Governing Documents
- Verification Constitution:
docs/verification-constitution.md— the 11 principles - Verification Guide:
docs/verification-guide.md— practical how-to - Verification Roadmap:
docs/verification-roadmap.md— strategic plan
Transition Policy
The verification constitution is being adopted incrementally. The existing test suite has ~3,500 tests that predate these standards. Do NOT rewrite or refactor existing tests to match the new standards unless explicitly asked. Apply the new standards to:
- New tests you are writing
- Tests you are modifying as part of a bug fix or feature
- Tests the user explicitly asks you to improve
Existing patterns (like assert result is not None) are not bugs to fix proactively — they are debt to address per the verification roadmap (docs/verification-roadmap.md).
Core Principles (from the Constitution)
- Documentation is the specification — every documented example is a verifiable claim
- Data correctness is existential — wrong numbers are the worst kind of bug
- The user's experience is the unit of verification — verify what users see, not internals
- Silence is the worst failure mode —
Nonewhere data was expected is a bug - Coverage means breadth of the SEC — diverse companies and forms over line counts
Definition of Done
Every new user-facing feature must include:
- Ground truth assertion — a specific value from a real SEC filing, verified by hand
assert revenue == 394328000000 # NOT: assert revenue is not None
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 · 124 lines · 0 tokens per session scan A fb90642e64ad
test-specialist is an agent published in the GitHub repository dgunning/edgartools (2,644 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,462 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.
Other agents, from other repositories
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-runner
Runs tests in the api-gateway Maven reactor — full/module unit runs, isolating a single core test class, or a single distribution/tutorial example test. Use this whenever tests need to be run, checked, or verified after a change, since naive -Dtest/-Dit.test invocations silently run (or skip) the wrong thing in this…
tester
Expert in Python testing, test coverage, mocking strategies, and PyMAPDL test infrastructure. Use for writing tests, improving coverage, fixing flaky tests, and reviewing test quality.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
tester
Use this agent to write and run tests for the sigcli project. This agent creates unit tests using vitest and MemoryStorage, following existing test patterns, and runs the full test suite. Examples.
unittest-generator
Use this agent when you need to create unit tests for your code in unittest.TestCase format, organized in a tests folder with concept-based subfolders. Examples: Context: User has just written a new authentication module and needs comprehensive unit tests. user: 'I just finished writing my user authentication…