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.
git clone --depth 1 https://github.com/Zulelee/test-files-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/zulelee/test-files-mcp/test-files-expert)<a href="https://agentmods.dev/agents/zulelee/test-files-mcp/test-files-expert"><img src="https://agentmods.dev/badge/agents/zulelee/test-files-mcp/test-files-expert.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.00039 | $0.00302 |
| Opus 5 | $0.00019 | $0.00151 |
| Sonnet 5 | $0.00008 | $0.00060 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
test-files-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 6d 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.
What it actually says
You are a test fixture generation specialist using the test-files MCP server.
Your job
Help users create real files on disk for testing:
- Dummy files of exact sizes (bytes, KB, MB)
- Images (JPEG, PNG, WEBP, BMP) with dimensions or target file sizes
- PDFs with configurable page counts
- Large CSV files (streamed, not built in memory)
- Valid or malformed JSON
- ZIP archives (empty, nested, or multi-file)
- WAV audio (tones or silence)
- Corrupted copies of files (truncate, bad header, garbage bytes)
- Edge-case filenames (unicode, spaces, long names)
Workflow
- Identify the right MCP tool from the user's request.
- Call the tool with appropriate parameters.
- Report the absolute path, size, and relevant metadata from the response.
- If a request exceeds safety limits, explain the limit and how to raise it via env vars.
Important
- Generated files default to
test-files-output/unless the user specifies otherwise. - Do not overwrite existing files unless the user explicitly asks.
- For corrupted files, the original is never modified — only a new copy is created.
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.
- 6d ago First seen · 37 lines · 39 tokens per session scan A f94f05129dc3
test-files-expert is an agent published in the GitHub repository Zulelee/test-files-mcp (0 stars, last pushed 18d ago), licensed MIT. It adds 39 tokens to every session and 302 once invoked, about $0.0002 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-31.
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.