Menu

Individual skill

ibkr

Keep an eye on an Interactive Brokers (IBKR) account or prices and speak up when something changes - new executions, prices crossing a level, option assignments and exercises, deposits and withdrawals, big moves in net asset value. Use when the user wants Codex to watch their IBKR account or IBKR market data, and when handling a fire of an IBKR trigger.

plugins/hyprh/self-starter/skills/ibkr/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Watch IBKR

Read the skill `self-starter:triggers` first for how triggers and fire messages work. There are two ways to watch IBKR; pick by what the user has.

## With IB Gateway and the ibkr skill (real time)

If the user runs IB Gateway or TWS on this machine and has the `ibkr` skill installed (Python scripts on `ib_async`, usually in a skills folder such as `~/.codex/skills/ibkr`; look for `scripts/trade/get_executions.py`), write a probe that runs its read-only scripts with `--json`. Probes run as the user, so they can call Python and reach the Gateway on 127.0.0.1.

- New executions (event mode): `python3 <skill>/scripts/trade/get_executions.py --json` prints `{"account", "count", "fills": [{"time", "contract", "side", "shares", "price", "exec_id", ...}]}` for today. Use `exec_id` as the event key.
- A price level (state mode): `python3 <skill>/scripts/quote/get_snapshot.py NVDA --json` prints `{"data": [{"symbol", "last", "close", "bid", "ask", ...}]}`.
- Positions and P&L: `scripts/trade/get_portfolio.py --json`, `scripts/trade/get_pnl.py --json`.
- Pass `IB_CLIENT_ID` in the command's environment with a number of its own (such as 2061), so the probe does not disconnect the user's own session, which uses the default. `IB_GATEWAY_PORT` picks paper (4002, the default) or live (4001); ask which one.
- On failure the scripts print `{"error": "..."}` and exit non-zero; throw it, so the user hears when the Gateway is down or logged out.
- A probe only reads. Never call `place_order.py`, `modify_order.py`, `cancel_order.py` or other trading scripts from a probe. If the user wants Codex to trade when the trigger fires, say that a fire in a background thread cannot ask for the confirmation live orders need, and make the task prepare the order and ask in the origin thread instead.