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/Esonhugh/ibkr-trade-analyzerWrote 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/commands/esonhugh/ibkr-trade-analyzer/analyze)<a href="https://agentmods.dev/commands/esonhugh/ibkr-trade-analyzer/analyze"><img src="https://agentmods.dev/badge/commands/esonhugh/ibkr-trade-analyzer/analyze.svg" alt="Measured on agentmods" 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.00013 | $0.00638 |
| Opus 5 | $0.00006 | $0.00319 |
| Sonnet 5 | $0.00003 | $0.00128 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
analyze 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 8d 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
Run targeted IBKR analysis using the section that best matches the user's intent.
Intent Routing
- P&L, profit, loss, drawdown, Sharpe, monthly returns →
sections=["pnl"]oribkr_pnl_summary. - Trading habits, win rate, frequency, holding period, profit factor →
sections=["trade"]oribkr_trade_patterns. - Holdings, allocation, concentration, cash, exposure →
sections=["portfolio"]oribkr_portfolio. - Fees, commissions, interest, dividends, fee drag →
sections=["cost"]oribkr_cost_analysis. - FX, currency conversion, non-base cash →
sections=["fx"]oribkr_fx_analysis. - Cost basis, breakeven, FIFO, LIFO, diluted cost →
sections=["diluted_cost"]oribkr_analyze.
Workflow
- Ensure data is loaded with
ibkr_fetch_data. - Map the user's words to the smallest section list that answers the question.
- Pass
periodandasset_typestoibkr_analyzewhen the user provides filters. - Use specialized tools for quick summaries when no filters are required.
Output Format
Return Markdown with these sections:
- Scope — data source, period, asset types, and selected sections.
- Findings — concise bullets grouped by selected section.
- Evidence Table — key metrics from the tool output.
- Limitations — missing fields, stale report timing, or unsupported filters.
Guardrails
- Ask a clarifying question only if the user's requested section cannot be inferred.
- Do not run all sections when one section is enough.
- Do not treat
priceas available throughibkr_analyze; the MCP analyzer sections aretrade,pnl,portfolio,cost,fx,diluted_cost, andchina_tax.
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.
- 8d ago First seen · 39 lines · 13 tokens per session scan A 4e0dcfb82ef6
analyze is a command published in the GitHub repository Esonhugh/ibkr-trade-analyzer (18 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 638 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 commands, from other repositories
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
scan
Scan AWS account for cost optimization.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…
audit
Scan for non-kernel money math. Rebuild critical flows as JournalEntrys. Replay and prove. Complements /ledger-verify.