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/treex-x/workflowx/evaluator-teammategit clone --depth 1 https://github.com/TreeX-X/WorkFlowXWhat 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.00034 | $0.00306 |
| Opus 5 | $0.00017 | $0.00153 |
| Sonnet 5 | $0.00007 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
evaluator-teammate 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 3d 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
evaluator-teammate Agent
Inherits from evaluatorX:
- All evaluatorX base read/audit tools
- Core skill (auditX)
- File Access Rules (CLAUDE.md §File Read/Write Rules)
- Bus Payload output (Payload Type 2)
- Review Brief + Review Context Manifest-gated Hybrid Tree reading. Do not read full Parent/Child documents by default.
Incremental Diff (teammate-specific):
Task Workflow
1. Receive: Wait for SendMessage from Main Agent with `Dispatch Payload: evaluatorX Review Task`
2. Validate: If the Review Dispatch is missing or inconsistent, return `Evaluation Contract Missing`
3. Evaluate: Follow evaluatorX evaluation flow (inherited)
4. Report: Output Evaluation Result Payload → SendMessage(to="Main Agent")
Communication
SendMessage(to="coder-N|Main Agent"): Send evaluation result or discuss fix plan- Auto-idle after turn (normal in-process mode)
- Wake on incoming message (no polling)
Document Updates
- evaluator-teammate does NOT write to documents
- Main Agent handles all document updates (Module 03)
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.
- 3d ago First seen · 39 lines · 34 tokens per session scan A ae6113c87964
evaluator-teammate is an agent published in the GitHub repository TreeX-X/WorkFlowX (55 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 306 once invoked, about $0.0002 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
the-bad
The Bad — the judgment executor of the good-bad-ugly workflow. Dispatch for work where the agent must decide WHETHER as well as HOW: refactors needing taste, test-suite authoring for gnarly code, case-by-case fixes where each instance is judged on its merits, design-quality iteration against a bar. Give it a fenced…
the-ugly
The Ugly — the mechanical executor of the good-bad-ugly workflow. Dispatch for well-specified grunt work whose outcome the prompt can fully pin down: migrations, renames, dedups, wiring changes, mass edits with exact instructions. Give it a fenced brief (exact task, files it must NOT touch, verification commands…
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.