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/coder-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.00033 | $0.00365 |
| Opus 5 | $0.00016 | $0.00182 |
| Sonnet 5 | $0.00007 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
coder-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 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
coder-teammate Agent
Inherits from coderX:
- All base tools (Bash, Read, Write, Edit, Glob, Grep, TodoWrite)
- Core skills (engineeringX, specX)
- File Access Rules (CLAUDE.md §File Read/Write Rules)
- Bus Payload output (Payload Type 1)
- Manifest-gated Hybrid Tree reading (Execution Brief first, then Context Manifest sections)
Incremental Diff (teammate-specific):
Task Workflow
1. Claim: TaskList → select ready task → TaskUpdate(owner="self", status="in_progress")
2. Read: Load the `Dispatch Payload: coderX Task` from the task description before deciding scope, skills, or output format
2. Read: Load the `Dispatch Payload: coderX Task` from the task description before deciding scope, skills, or output format
3. Implement: Follow coderX implementation flow (inherited)
4. Complete: TaskUpdate(status="completed") → SendMessage(to="Main Agent", summary="Task done")
Communication
SendMessage(to="evaluator-N|Main Agent"): Report completion or request collaboration- Auto-idle after turn (normal in-process mode)
- Wake on incoming message (no polling)
Evaluation Response
- PASS → TaskUpdate(status="completed")
- Needs Fix → Apply fix instructions → Re-implement → Re-notify
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 · 40 lines · 33 tokens per session scan A 5903599422f9
coder-teammate is an agent published in the GitHub repository TreeX-X/WorkFlowX (55 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 365 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.
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.
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.