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/ed3dai/ed3d-pluginsWrote 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/ed3dai/ed3d-plugins/test-analyst)<a href="https://agentmods.dev/agents/ed3dai/ed3d-plugins/test-analyst"><img src="https://agentmods.dev/badge/agents/ed3dai/ed3d-plugins/test-analyst/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.
<a href="https://agentmods.dev/agents/ed3dai/ed3d-plugins/test-analyst"><img src="https://agentmods.dev/badge/agents/ed3dai/ed3d-plugins/test-analyst.svg" alt="Reviewed on agentmods" width="80" 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.00040 | $0.00737 |
| Opus 5.5 | $0.00016 | $0.00295 |
| Sonnet 5.5 | $0.00008 | $0.00147 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
test-analyst 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 1mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 1mo ago First seen · 108 lines · 40 tokens per session scan A 11f610bb0d17
test-analyst is an agent published in the GitHub repository ed3dai/ed3d-plugins (252 stars, last pushed 1mo ago), with no licence file. It adds 40 tokens to every session and 737 once invoked, about $0.0002 per session on Opus 5.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-30.
Other agents, from other repositories
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.
verify-app
Verification expert. Proactively runs tests after code changes, analyzes failures, and suggests fixes.
pact-implementor
Specialized agent for building a new Pact client library from scratch in any language. Invoke this agent when the user wants to create a Pact implementation for a language that doesn't have one yet — such as Pact Zig, Pact Lua, Pact Elixir, Pact Nim, Pact V, Pact Odin, or any other language. Also invoke when the user…
bdct-tester
Agentic BDCT (Bi-Directional Contract Testing) driver. Invoke this agent when the user wants to implement a full BDCT flow end-to-end: it generates high-coverage consumer Pact tests and a provider OpenAPI contract, publishes both to PactFlow, runs cross-contract verification, and loops — diagnosing failures and fixing…
pact-maintainer
Pact ecosystem maintenance agent. Invoke when the user wants to audit the health of their PactFlow workspace, fix failing verifications, clean up stale branches or old versions, update consumer tests after an API change, manage environments and webhooks, diagnose can-i-deploy failures, or get a full health report…
pact-coverage
Runs Pact consumer coverage. Uses ripwire MCP tools on the consumer codebase to discover which provider API routes the consumer calls, builds a consumer-filtered provider OAS, then runs parsepactcoverage.py to report gaps (operations/codes/ fields the consumer uses but hasn't exercised in any pact interaction).