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/endorphin-ai/claude-code-teamsWrote 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/endorphin-ai/claude-code-teams/tester-react)<a href="https://agentmods.dev/agents/endorphin-ai/claude-code-teams/tester-react"><img src="https://agentmods.dev/badge/agents/endorphin-ai/claude-code-teams/tester-react/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/endorphin-ai/claude-code-teams/tester-react"><img src="https://agentmods.dev/badge/agents/endorphin-ai/claude-code-teams/tester-react.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.00101 | $0.02081 |
| Opus 5.5 | $0.00040 | $0.00832 |
| Sonnet 5.5 | $0.00020 | $0.00416 |
| Haiku 4.5 | $0.00010 | $0.00208 |
Grade A, and why
tester-react 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 · 197 lines · 101 tokens per session scan A b77ef71fb19e
tester-react is an agent published in the GitHub repository endorphin-ai/claude-code-teams (3 stars, last pushed 7mo ago), with no licence file. It adds 101 tokens to every session and 2,081 once invoked, about $0.0004 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-31.
Other agents, from other repositories
qa-loop
Autonomous audit-fix loop aligned with the Anthropic 2026 pattern (code-review plugin). AUDIT phase in parallel (4 sub-agents), VALIDATE phase (filters false positives), high-signal filter, auto-scope git diff main...HEAD. Flags --audit-only and --comment for read-only and inline PR post modes.
qa-e2e
End-to-End tests with Playwright or Cypress. Use to create complete user journey tests.
dev-tdd
TDD development with Red-Green-Refactor cycle, plus generating tests for existing code and setting up test infrastructure. Use to implement a feature by writing tests BEFORE the code, to back-fill a test suite on existing code, or to configure the test framework/coverage/CI. Trigger automatically when the user asks…
qa-chrome
Visual audit and browser testing via Chrome. Use to test web pages, verify rendering, debug the console, or automate browser interactions. Requires the --chrome flag.
verifier
Verifies that a change actually works — runs the verification command, reads real output, reports PASS / PARTIAL / FAIL with quoted evidence. Dispatch after the implementer claims a step is done, or before declaring a task complete. Context: The implementer just reported a task done. user: (post-implementer gate)…
bug-verifier
Verify bug fixes by running tests. Final step in bug fix pipeline.