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/crypto-com/cdcx-cli/cdcx-place-limit-ordernpx skills add crypto-com/cdcx-cli --skill cdcx-place-limit-ordergit clone --depth 1 https://github.com/crypto-com/cdcx-cliWrote 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/skills/crypto-com/cdcx-cli/cdcx-place-limit-order)<a href="https://agentmods.dev/skills/crypto-com/cdcx-cli/cdcx-place-limit-order"><img src="https://agentmods.dev/badge/skills/crypto-com/cdcx-cli/cdcx-place-limit-order.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 | $0.00029 | $0.01169 |
| Opus 5 | $0.00015 | $0.00584 |
| Sonnet 5 | $0.00006 | $0.00234 |
| Haiku 4.5 | $0.00003 | $0.00117 |
Grade A, and why
cdcx-place-limit-order 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 5d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Place Limit Order
When to Use
- Patient entry at a specific price
- Split a large order into laddered rungs
- Anchor a position before attaching stop/take-profit legs
Requires authentication. Order placement is tier mutate.
The Command
cdcx trade order <SIDE> <INSTRUMENT> <QUANTITY> \
--type LIMIT --price <PRICE> \
[--time-in-force GOOD_TILL_CANCEL|FILL_OR_KILL|IMMEDIATE_OR_CANCEL|POST_ONLY] \
[--client-oid <ID>] \
[--exec-inst POST_ONLY|REDUCE_ONLY|SMART_POST_ONLY|ISOLATED_MARGIN]
Positional args: <side> <instrument_name> <quantity>. Side is BUY or SELL. Omitting --type defaults to MARKET.
Preflight (mandatory before going live)
# 1. Verify auth
cdcx account info -o json > /dev/null
# 2. Cash check
cdcx account summary -o json | \
jq -r '.data.total_available_balance'
# 3. Instrument is tradable + get tick sizes
cdcx market instruments -o json | \
jq '.data.data[] | select(.symbol=="BTC_USDT") |
{symbol, price_tick_size, qty_tick_size, min_qty, max_qty, tradable}'
# 4. Current market context
cdcx market ticker BTC_USDT -o json | \
jq '.data[0] | {last:.a, bid:.b, ask:.k, high:.h, low:.l}'
cdcx market book BTC_USDT --depth 10 -o json
Dry-Run (free preview)
cdcx trade order BUY BTC_USDT 0.1 \
--type LIMIT --price 50000 \
--client-oid buy-btc-$(date +%s) \
--dry-run -o json
--dry-run prints the signed request body without sending it. Inspect to confirm every field is correct.
Place
cdcx trade order BUY BTC_USDT 0.1 \
--type LIMIT --price 50000 \
--time-in-force GOOD_TILL_CANCEL \
--client-oid buy-btc-2026-04-17 \
-o json
Response includes order_id. Store both order_id and your client_oid — either can be used to look up or cancel.
Monitor
# List open orders for this instrument
cdcx trade open-orders BTC_USDT -o json
# Get full detail for one
cdcx trade order-detail <ORDER_ID> -o json
# or
cdcx trade order-detail --client-oid buy-btc-2026-04-17 -o json
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.
- 5d ago First seen · 144 lines · 29 tokens per session scan A c8cedbc230b2
cdcx-place-limit-order is a skill published in the GitHub repository crypto-com/cdcx-cli (25 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 1,169 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 skills, from other repositories
sector-rotation
行业轮动分析——申万行业景气度评分、行业动量排名、产业链传导、估值/盈利/资金流多维比较框架.
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…
strategy-pivot-designer
Detect backtest iteration stagnation and generate structurally different strategy pivot proposals when parameter tuning reaches a local optimum.
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.
trading-risk-gate
Unified pre-trade safety gate: Ruin check (Law #1), ergodicity audit, and win-rate dominance validation. Absorbs: ergodicity-check, law-of-ruin, win-rate-dominance.
vectorbt
High-performance vectorized backtesting with parameter optimization, portfolio simulation, and rich performance metrics.