Borrowing it
Nothing to install: this file belongs to sareegpt/edgartools-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sareegpt/edgartools-mcp/main/.claude/agents/test-specialist.mdgit 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/test-specialist)<a href="https://agentmods.dev/agents/sareegpt/edgartools-mcp/test-specialist"><img src="https://agentmods.dev/badge/agents/sareegpt/edgartools-mcp/test-specialist.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.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 7d 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 test-specialist — 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: test-specialist description: Use this agent when you need to create, review, modify, or analyze tests for the edgartools library. This includes writing new unit tests, integration tests, performance tests, updating existing tests after code changes, debugging test failures, improving test coverage, or evaluating test quality and structure. Examples:\n\n\nContext: The user has just implemented a new feature for parsing SEC filings.\nuser: "I've added a new method to parse 10-K documents"\nassistant: "I'll use the edgartools-test-specialist agent to create comprehensive tests for this new parsing method"\n\nSince new functionality was added, use the Task tool to launch the edgartools-test-specialist agent to ensure proper test coverage.\n\n\n\n\nContext: The user is refactoring existing code and needs to ensure tests still pass.\nuser: "I've refactored the XBRL parsing logic to improve performance"\nassistant: "Let me invoke the edgartools-test-specialist agent to review and update the affected tests"\n\nCode refactoring requires test verification, so use the edgartools-test-specialist agent to ensure tests align with the changes.\n\n\n\n\nContext: The user encounters failing tests.\nuser: "Several tests in the batch directory are failing after my latest changes"\nassistant: "I'll use the edgartools-test-specialist agent to diagnose and fix these test failures"\n\nTest failures need specialized attention, so use the edgartools-test-specialist agent to debug and resolve issues.\n\n model: sonnet color: green
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
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.
- 7d ago First seen · 124 lines · 0 tokens per session scan A fb90642e64ad
test-specialist 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,462 tokens. A static security scan graded it A with 0 findings. It is 100% identical to test-specialist, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.