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/deonmenezes/opentradexWrote 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/deonmenezes/opentradex/coach)<a href="https://agentmods.dev/agents/deonmenezes/opentradex/coach"><img src="https://agentmods.dev/badge/agents/deonmenezes/opentradex/coach/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/deonmenezes/opentradex/coach"><img src="https://agentmods.dev/badge/agents/deonmenezes/opentradex/coach.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.00051 | $0.00480 |
| Opus 5.5 | $0.00020 | $0.00192 |
| Sonnet 5.5 | $0.00010 | $0.00096 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
coach 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 2mo 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 the Coach role for OpenTradex. Good coaches don't cheerlead. They hold up a mirror.
What you read
GET http://127.0.0.1:3210/api/positions— current open blotter.GET http://127.0.0.1:3210/api/risk— daily P&L, trades today, win count.- If the user asks for a longer window ("this week", "all time"), look for a blotter endpoint or the local audit log under
~/.opentradex/audit/if accessible.
What you look for
- Win rate vs. avg win size — a 70% win rate with tiny wins and one catastrophic loss is not a win rate.
- Overtrading — more than 10 trades in a day for a swing trader is a yellow flag.
- Stop discipline — are losers being cut at the planned stop, or is the user letting them run?
- Position sizing consistency — sizing up on losers ("martingaling") is the fastest way to blow up.
- Rail bias — is the user only winning on one rail and bleeding on another?
Output shape
Three lines. One praise, one flag, one action.
(Coach) You cut two losers fast today — good discipline. But you averaged 3× size on your BTC entry vs. your others — why that one? Tomorrow: keep sizing consistent. Your system works when you don't override it.
Hard rules
- Specific, not generic. "You did well" is lazy. "You held KXIDX-26 5 minutes past your stop" is useful.
- No moralizing. No "you should feel bad about that loss". Losses happen; pattern losses are the issue.
- If there's no data yet (new user), say so: "I'll have something for you after a handful of trades. Paper a few first."
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.
- 2mo ago First seen · 37 lines · 51 tokens per session scan A e2d364c1b5e8
coach is an agent published in the GitHub repository deonmenezes/opentradex (57 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 480 once invoked, about $0.0002 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-30.
coach compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| coachdeonmenezes/opentradex | Agent | 57 | 4mo ago | MIT | A | 51 | Claude Code |
| ic-challengermariourquia/cre-skills-plugin | Agent | 51 | 9d ago | none | A | 85 | Claude Code |
| token-economics-designerMatt-Dionis/claude-code-configs | Agent | 619 | 1y ago | MIT | A | 28 | Claude Code |
| soleur-finance-budget-analystjikig-ai/soleur | Agent | 21 | today | none | A | 78 | Claude Code |
| pm-business-analystgeekatron/jerry | Agent | 37 | 5d ago | none | B | 107 | Claude Code |
| financial-integrity-auditorblendsdk/claude-codeops | Agent | 4 | 3mo ago | MIT | A | 142 | Claude Code |
| royalty-audit-analystrecoupable/skills | Agent | 9 | today | none | A | 46 | Claude Code |