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 skills/nutdnuy/webull-openapi-ai-plugin/webull-authnpx skills add nutdnuy/webull-openapi-AI-Plugin --skill webull-authgit clone --depth 1 https://github.com/nutdnuy/webull-openapi-AI-PluginWhat 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.00054 | $0.00683 |
| Opus 5 | $0.00027 | $0.00342 |
| Sonnet 5 | $0.00011 | $0.00137 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
webull-auth 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Webull authentication
Read references/authentication.md, the matching references/endpoints.json entry, and its schema_ref in references/openapi.json before constructing any request. Use the official Webull Open API reference for current details.
First-use onboarding
Before the first API request, check whether WEBULL_APP_KEY and WEBULL_APP_SECRET are available through the configured environment or secret manager. If WEBULL_APP_KEY is missing, stop and ask the user to configure the Webull API Key securely before continuing. Never ask the user to paste the App Secret or access token into chat.
Supported endpoints
POST /openapi/auth/token/create— official reference index. Treat token creation as a sensitive write-like operation: require explicitTOKEN_WRITEconfirmation immediately before calling it.POST /openapi/auth/token/check— official reference index. The catalog marks this as a credential-status read; still handle token material as secret.
Workflow
-
Load only the required environment variables from a local secret manager or shell environment. Never ask the user to paste a secret into chat, never print secrets, and redact tokens, signatures, authorization headers, and response fields containing credential material.
-
Read the catalog entry to determine the HTTP method, required headers, query parameters, and JSON body. Do not invent fields or copy a neighboring endpoint’s schema.
-
For token creation, summarize the intended operation and wait for exact
TOKEN_WRITEconfirmation; then invoke the shared runtime, for example:python scripts/webull_api.py request --method POST --path /openapi/auth/token/create --body-file ./token-create.json -
For status checks, invoke the catalog-shaped request only after confirming the token is available through the configured secret source. No write gate is required because this endpoint is cataloged as
risk: read:
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.
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 · 41 lines · 54 tokens per session scan A 66092d1d4311
webull-auth is a skill published in the GitHub repository nutdnuy/webull-openapi-AI-Plugin (26 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 683 once invoked, about $0.0003 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 skills, from other repositories
twitter-reader
Read Twitter/X for financial research using opencli (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my…
chenhao-limit-up
Use when evaluating A-share limit-up (涨停板) setups through Chen Hao's sentiment and momentum lens: market emotion cycles, board strength, follow-through, and short-term aggressive momentum trading.
copy-trading-solana
Copy trade Solana wallets - mirror trades automatically.
southwest
Search Southwest Airlines fares and points pricing via Patchright browser automation. SW is not in any GDS or API. Covers all fare classes, Companion Pass value, and fare drop monitoring.
alpaca-trade-api-sdk
Integrate and build on the @alpacahq/alpaca-trade-api TypeScript SDK for the Alpaca Trading and Market Data APIs (the unified Alpaca client, ergonomic order builders, normalized market-data shapes, pagination, typed errors, resilience, and real-time streaming). Use when writing or reviewing code that imports…
alphagbm-greeks
Greeks dashboard for any option contract or multi-leg position. Covers first-order Greeks (Delta, Gamma, Theta, Vega, Rho) and second-order Greeks (Charm, Vanna, Volga). Returns individual and position-level Greeks with scenario heatmaps. Use when: checking option sensitivities, managing position risk, understanding…