IBKR CLI
v1.0.0Comprehensive Interactive Brokers (IBKR) TWS/Gateway skill using ib_insync. Includes Python and bash CLIs for account, market data, historical data, contract...
⭐ 0· 587·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description describe an IBKR CLI and the repository contains Python and bash CLIs, legacy wrappers, and tests that implement account queries, market data, historical data, contract lookup, scanners, and order placement — all consistent with the stated purpose.
Instruction Scope
SKILL.md and the scripts limit actions to connecting to TWS/IB Gateway and performing IB operations. One notable capability: the CLI can place and cancel real orders, so use with caution (test in paper mode). The instructions do not attempt to read unrelated files or exfiltrate data to third-party endpoints; connection parameters can be overridden to point at arbitrary hosts (by design) — ensure you don't point it to untrusted remote endpoints.
Install Mechanism
No install spec is provided (instruction-only for environment setup). The SKILL.md recommends installing the well-known ib_insync package from PyPI; there are no downloads from arbitrary URLs or extract/remote install steps in the manifest.
Credentials
No required secrets or config paths are declared. The code accepts optional IBKR_HOST/IBKR_PORT/IBKR_CLIENT_ID/IBKR_ACCOUNT environment variables (documented) which are appropriate for configuring an IB connection. No unrelated credentials or high-privilege environment access is requested.
Persistence & Privilege
Skill is not always-enabled and does not request persistent or elevated platform privileges. It does perform actions (including placing orders) when invoked, which is expected for a trading CLI.
Assessment
This skill appears to do exactly what it claims: a local CLI for Interactive Brokers via ib_insync. Before installing/use: 1) Review and run tests in a safe environment (paper account) — the CLI can place/cancel real orders. 2) Install ib_insync from PyPI (pip install ib_insync) rather than running unknown install scripts. 3) Keep IBKR_HOST default (127.0.0.1) unless you intentionally want to connect to a remote IB Gateway/TWS; do not point it to untrusted remote hosts. 4) Inspect the code yourself if you are concerned — there are no obfuscated network calls or hidden endpoints, but trade-capable scripts carry financial risk if misused.Like a lobster shell, security has layers — review code before you run it.
latestvk973qet3f7pthhr5nasqg3qy9581z54t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
