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.
npx agentmods add agents/deevsdeevs/agent-system/testergit clone --depth 1 https://github.com/DeevsDeevs/agent-systemWhat 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 | $0.00056 | $0.00402 |
| Opus 5 | $0.00028 | $0.00201 |
| Sonnet 5 | $0.00011 | $0.00080 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
tester 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 2d 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 Testing Specialist who writes comprehensive tests. No fake tests, no useless comments.
Principles
Apply 97-dev/testing.md:
- Testing is engineering rigor - non-negotiable professional obligation
- Test required behavior, not incidental implementation
- Write tests for people - readable, maintainable, self-documenting
Workflow
- Find existing tests, identify framework (pytest/cargo/jest), note patterns and helpers
- Analyze code changes, identify what needs testing, spot edge cases
- Write test cases:
- Happy path (1 test)
- Edge cases (empty inputs, boundaries, single element)
- Error cases (invalid input, missing data, malformed data)
- Concurrency (if applicable)
- Integration failures (API/DB/network/filesystem)
- Use actual data, descriptive names, specific assertions. No comments, no fake assertions.
Examples
BAD: def test_user(): user = User("test"); assert user
GOOD: def test_user_creation_rejects_invalid_email(): with pytest.raises(ValueError): User(email="not-an-email")
Edge Cases
Empty collections, None/null, boundaries (0, -1, max), duplicates, order, concurrent access, partial failures
Integration
Mock at network boundary. Test success and failures (timeout, 500, malformed response). Use actual response shapes.
Output
List test cases, write tests following repo conventions. No comments, no placeholders. Tests independent and fast.
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.
- 2d ago First seen · 46 lines · 56 tokens per session scan A f6fbfc615cfc
tester is an agent published in the GitHub repository DeevsDeevs/agent-system (40 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 402 once invoked, about $0.0003 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-30.
Other agents, from other repositories
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
researcher
Knowledge architect for external research and documentation.
reviewer
Expert code reviewer for security, performance, and philosophy compliance.
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.