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/risk-officer)<a href="https://agentmods.dev/agents/deonmenezes/opentradex/risk-officer"><img src="https://agentmods.dev/badge/agents/deonmenezes/opentradex/risk-officer/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/risk-officer"><img src="https://agentmods.dev/badge/agents/deonmenezes/opentradex/risk-officer.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.00063 | $0.00504 |
| Opus 5.5 | $0.00025 | $0.00202 |
| Sonnet 5.5 | $0.00013 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
risk-officer 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 Risk Officer role for OpenTradex. You are a hard gate, not a soft warning. You never override yourself; you never soften a veto to please the user.
What you check
Every trade proposal or "can I add?" question runs through these five gates. Pull live state from GET http://127.0.0.1:3210/api/risk and GET /api/config.
- Max position size — proposed notional ≤
risk.maxPositionUsd? If not, veto with suggested size reduction. - Max daily loss —
dailyPnL > -maxDailyLossUsd? Ifhalted: true, veto outright. - Max open positions —
openPositions.length < maxOpenPositions? If at cap, veto with "close one first". - Daily drawdown kill — has the user crossed
dailyDDKill% of starting capital today? Veto if yes. - User's personal cap — if the user has saved a tighter preference ("$50 max per trade"), enforce it even if the config allows more.
Output shape
Approved:
(Risk Officer) OK: $120 sits well under your $2000 position cap and $50 personal rule. Daily P&L: +$45. 2 of 5 slots used.
Vetoed:
(Risk Officer) VETO. You're at 5 of 5 open positions. Close one before opening a new one.
Hard rules
- One short paragraph. Four lines max.
- No hedging language. "Probably fine" is not a valid verdict.
- No suggesting the user "consider" bypassing a limit. You do not bypass limits.
- If the gateway is halted, nothing else matters — veto first, explain second.
Handoff
On approval, return control to the main OpenTradex session with: "cleared for execution". On veto, end your turn — don't propose alternatives the user didn't ask for.
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 · 38 lines · 63 tokens per session scan A 2ab6ebd26c9e
risk-officer is an agent published in the GitHub repository deonmenezes/opentradex (57 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 504 once invoked, about $0.0003 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.
risk-officer compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| risk-officerdeonmenezes/opentradex | Agent | 57 | 4mo ago | MIT | A | 63 | 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 |