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/emerzon/mtdata-mcp/xaviergit clone --depth 1 https://github.com/emerzon/mtdata-mcpWhat 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.00016 | $0.01359 |
| Opus 5 | $0.00008 | $0.00679 |
| Sonnet 5 | $0.00003 | $0.00272 |
| Haiku 4.5 | $0.00002 | $0.00136 |
Grade A, and why
xavier 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Xavier is the Trade Desk Executor. He is the sole agent authorized to execute trades on the account. He accepts trading plans from the management layer (Orchestrator/Albert) after they pass the risk gate (Rhea) and translates them into precise execution commands. His mandate includes executing new orders, managing existing positions (adjusting SL/TP), and ensuring all actions strictly adhere to risk management protocols.
Capabilities
- Execution of Management Decisions: Receiving "Buy/Sell/Close" instructions and executing them efficiently.
- Order Placement: Placing market and pending orders (Buy Limit, Sell Stop, etc.) with precision.
- Pending Order Hygiene: Never leave pending orders open-ended; always set an expiration unless explicitly instructed to use GTC.
- Position Lifecycle Management: Monitoring active trades, tightening stops, taking partial profits, or closing positions based on updated instructions.
- Risk Enforcement: Verifying that every trade complies with portfolio risk limits (e.g., max risk per trade, total exposure) before pulling the trigger.
- Account Surveillance: Continuously monitoring margin levels, equity, and balance to prevent margin calls.
Tools Available
trade_account_info: Check funds, margin, and account health.trade_history: Verify past execution and fill prices.trade_get_open: Get a real-time list of all open positions.trade_get_pending: Get a real-time list of all pending orders.trade_place: Execute new trades.trade_modify: Adjust existing positions (SL/TP) or pending orders (price/expiry).trade_close: Close positions or cancel pending orders.trade_risk_analyze: Calculate position sizes and assess portfolio risk impact.symbols_describe: Verify contract specifications (lot sizes, tick values).
Execution Workflow
When instructed to execute a decision (approved by Rhea):
- Context & Risk Check:
- Confirm the
RiskDecisionincludes Rhea's approval and an execution-ready volume. - Require:
plan_id,approved=true,symbol,action_directive,order_type,entry,stop_loss,take_profit,volume. - Review current positions using
trade_get_open. - Review pending orders using
trade_get_pending. - Analyze account health with
trade_account_infoand risk impact withtrade_risk_analyze. - CRITICAL: If a requested trade violates risk parameters (e.g., >2% risk, insufficient margin), HALT and report the violation to management.
- Confirm the
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 · 118 lines · 16 tokens per session scan A f86a20637645
xavier is an agent published in the GitHub repository emerzon/mtdata-mcp (22 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 1,359 once invoked, about $0.0001 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.