What is webull-orders?

A guarded tool for viewing and managing stock orders through Webull Thailand. It supports previews, order history, open orders, details, placing, changing, and cancelling orders.

Use it to preview a Webull order, inspect existing orders, check order history, or place, replace, and cancel an order after clear confirmation.

It separates research from actual trading and requires explicit safety checks before an order is written. This helps prevent accidental purchases, changes, or cancellations.

webull-orders — Skill by nutdnuy

Install

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.

agentmods

npx agentmods add skills/nutdnuy/webull-openapi-ai-plugin/webull-orders

Any agent

npx skills add nutdnuy/webull-openapi-AI-Plugin --skill webull-orders

Clone the repo

git clone --depth 1 https://github.com/nutdnuy/webull-openapi-AI-Plugin

Made for: Claude Code, Codex.

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 712 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00048	$0.00712
Opus 5	$0.00024	$0.00356
Sonnet 5	$0.00010	$0.00142
Haiku 4.5	$0.00005	$0.00071

Measured 2d ago against content hash 8ac88150c520, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

webull-orders 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.

skills/webull-orders/SKILL.md · 43 lines

How it starts

The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Webull orders

Read the exact endpoint entry in references/endpoints.json, follow its schema_ref into references/openapi.json, and read authentication rules in references/authentication.md before building any request. Use the official Webull Open API reference and current trading documentation.

First-use onboarding

Before any order-related request, check for WEBULL_APP_KEY and WEBULL_APP_SECRET in the secure environment. If the API Key is missing, ask the user to configure it securely and stop; never request credentials in chat. Require an active WEBULL_ACCESS_TOKEN before preview or any order operation.

Supported endpoints

POST /openapi/trade/order/preview — preview only; gate with PREVIEW.
POST /openapi/trade/order/place — write; require exact confirmation and PLACE.
POST /openapi/trade/order/replace — write; require exact confirmation and REPLACE.
POST /openapi/trade/order/cancel — write; require exact confirmation and CANCEL.
GET /openapi/trade/order/history — read-only history.
GET /openapi/trade/order/open — read-only open orders.
GET /openapi/trade/order/detail — read-only detail.

All paths are documented in the official reference index.

Safety workflow

For preview, obtain the exact user-provided instrument, side, quantity, order type, price/trigger, time-in-force, account, and other catalog-required fields. Read the catalog before constructing the body, then ask for PREVIEW confirmation:
```
python scripts/webull_api.py request --method POST --path /openapi/trade/order/preview --body-file ./order-preview.json --allow-write --write-confirmation PREVIEW
```
Before place, replace, or cancel, display a concise request-payload summary: environment, account (redacted), symbol, side, quantity, order type, price/trigger, time-in-force, client order id, and the exact operation. Do not execute until the user gives the corresponding exact gate: PLACE, REPLACE, or CANCEL.
Construct each body independently from references/endpoints.json; never copy preview output blindly into a write request and never infer missing fields. Invoke only after confirmation, using the documented method/path:

Read the full file on GitHub · 43 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

agents/openai.yaml 208 B

Changes

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 · 43 lines · 48 tokens per session scan A 8ac88150c520

Subscribe to this mod's changes

webull-orders is a skill published in the GitHub repository nutdnuy/webull-openapi-AI-Plugin (26 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 712 once invoked, about $0.0002 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.

Productivity Research

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens