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/BingHanOfUESTC/open_agent_teamWrote 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/binghanofuestc/open_agent_team/test_gap_agent)<a href="https://agentmods.dev/agents/binghanofuestc/open_agent_team/test_gap_agent"><img src="https://agentmods.dev/badge/agents/binghanofuestc/open_agent_team/test_gap_agent/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/binghanofuestc/open_agent_team/test_gap_agent"><img src="https://agentmods.dev/badge/agents/binghanofuestc/open_agent_team/test_gap_agent.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.00029 | $0.00105 |
| Opus 5.5 | $0.00012 | $0.00042 |
| Sonnet 5.5 | $0.00006 | $0.00021 |
| Haiku 4.5 | $0.00003 | $0.00011 |
Grade A, and why
test_gap_agent 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.
What it actually says
test_gap_agent
必须使用 skills/bug-risk-review/SKILL.md，重点输出测试缺口。
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 · 16 lines · 29 tokens per session scan A b72bb7e92335
test_gap_agent is an agent published in the GitHub repository BingHanOfUESTC/open_agent_team (106 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 105 once invoked, about $0.0001 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
imperial-censor
An independent code-review and testing role for Java projects. It writes tests from the project rules before implementation, then checks the finished code against those rules across seven review areas.
test-analyzer
Test coverage agent for CI: reviews PR diffs for missing test coverage, untested edge cases, inadequate error path testing, and test quality issues. Focuses on behavioral coverage over line metrics.
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Typical triggers include the user asking whether tests on a freshly-created PR are thorough…
quality-gatekeeper
Orchestrates quality assurance workflows, enforcing code standards, linting, testing, and security checks prior to merges. Proactively manages multi-agent review workflows.
karimo-tester
Writes and maintains tests (complexity 1-4) for KARIMO task outputs. Creates unit tests, integration tests, validates coverage. Use for straightforward test-specific tasks.
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.