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-go)<a href="https://agentmods.dev/agents/endorphin-ai/claude-code-teams/tester-go"><img src="https://agentmods.dev/badge/agents/endorphin-ai/claude-code-teams/tester-go/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-go"><img src="https://agentmods.dev/badge/agents/endorphin-ai/claude-code-teams/tester-go.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.00102 | $0.01921 |
| Opus 5.5 | $0.00041 | $0.00768 |
| Sonnet 5.5 | $0.00020 | $0.00384 |
| Haiku 4.5 | $0.00010 | $0.00192 |
Grade A, and why
tester-go 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 · 182 lines · 102 tokens per session scan A 7b55f633d7e5
tester-go 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 102 tokens to every session and 1,921 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
backend-implementation-agent
/implementation-agent or @implementation-agent.
test-writer
Writes thorough tests for existing code. Detects test framework from project config, reads CLAUDE.md first, follows existing test patterns. Handles unit, integration, and e2e tests. Designed for parallel execution with isolation: worktree.
check-writer
Creates or reviews check modules in src/checks/, making sure they follow the buildResult pattern and have a corresponding test.
test-generator
Use this agent to write tests for existing code, generate test suites, add unit tests, integration tests, or when the user says "write tests for", "add tests", "test coverage", "generate test cases".
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
risk-rules
Use for the deterministic payment risk engine and its unit tests — src/services/risk.service.ts and its spec file. Invoke when writing, editing, or testing any risk rule. Do not use for tools, widgets, guards, or anything involving I/O.