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 skills add xbotlive/btse-mcp --skill btse-placing-ordersgit clone --depth 1 https://github.com/xbotlive/btse-mcpWrote 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/xbotlive/btse-mcp/btse-placing-orders)<a href="https://agentmods.dev/skills/xbotlive/btse-mcp/btse-placing-orders"><img src="https://agentmods.dev/badge/skills/xbotlive/btse-mcp/btse-placing-orders/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/xbotlive/btse-mcp/btse-placing-orders"><img src="https://agentmods.dev/badge/skills/xbotlive/btse-mcp/btse-placing-orders.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00030 | $0.01135 |
| Opus 5.5 | $0.00012 | $0.00454 |
| Sonnet 5.5 | $0.00006 | $0.00227 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
btse-placing-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 2mo 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BTSE Placing Orders
Orders are irreversible once filled. Always follow the pre-flight checklist.
Pre-Flight Checklist (Every Order)
- Confirm environment — call
btse_get_price("BTC-PERP")and check the price is realistic for testnet vs live - Check account — call
btse_account_overview()to see balance and existing exposure - State the order to the user — symbol, side, size, type, price (if limit)
- Get explicit confirmation before calling any order tool
- Use the
place_order_guideprompt for a fully guided flow
Order Types
| Type | When to use | Required fields |
|---|---|---|
MARKET |
Fill immediately at best available price | symbol, side, size |
LIMIT |
Fill at a specific price or better | symbol, side, size, price |
OCO |
One-Cancels-Other: TP + SL in one order | symbol, side, size, take_profit_price, stop_loss_price |
Placing a Market Order (Safe Method)
Always prefer this over btse_create_order for market orders:
btse_safe_market_order(
symbol="BTC-PERP",
side="BUY",
size=0.01,
expected_price=85000, # price you're expecting to fill near
max_slippage_pct=0.5, # abort if market has moved more than 0.5%
reduce_only=False
)
If the current price is more than max_slippage_pct away from expected_price, the order is not submitted and an error is returned. Ask the user to confirm the new price before retrying.
Placing a Limit Order
btse_create_order(
symbol="BTC-PERP",
side="BUY",
order_type="LIMIT",
size=0.01,
price=84000,
time_in_force="GTC", # GTC | IOC | FOK | DAY | WEEK | MONTH
post_only=False,
reduce_only=False
)
Placing an OCO Order
btse_create_order(
symbol="BTC-PERP",
side="SELL",
order_type="OCO",
size=0.01,
take_profit_price=90000,
stop_loss_price=80000
)
Viewing Orders
# All open orders (optionally filter by symbol)
btse_get_open_orders(symbol="BTC-PERP")
# Single order by ID
btse_get_order(order_id="abc123")
btse_get_order(cl_order_id="my-custom-id")
# Trade fill history
btse_get_trade_history(symbol="BTC-PERP", count=20)
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.
- 2mo ago First seen · 162 lines · 30 tokens per session scan A de83da2371d8
btse-placing-orders is a skill published in the GitHub repository xbotlive/btse-mcp (0 stars, last pushed 8mo ago), licensed MIT. It adds 30 tokens to every session and 1,135 once invoked, about $0.0001 per session on Opus 5.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-31.
btse-placing-orders compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| btse-placing-ordersxbotlive/btse-mcp | Skill | 0 | 8mo ago | MIT | A | 30 | Claude Code, Codex |
| sector-rotationHKUDS/Vibe-Trading | Skill | 38k | today | MIT | A | 39 | Claude Code, Codex |
| strategy-pivot-designertradermonty/claude-trading-skills | Skill | 3.7k | today | MIT | A | 28 | Claude Code, Codex |
| twitter-readerhimself65/finance-skills | Skill | 3.5k | 4d ago | MIT | A | 110 | Claude Code |
| energy-procurementhashgraph-online/awesome-codex-plugins | Skill | 1.5k | today | Apache-2.0 | A | 93 | Claude Code, Codex |
| airdrop-hunting-guidenirholas/three.ws | Skill | 271 | today | Apache-2.0 | A | 54 | Claude Code, Codex |
| multi-expert-analyzerdigoal/blog | Skill | 8.6k | 4d ago | GPL-2.0 | A | 292 | Codex |