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/chainstacklabs/polymarket-alpha-bot/alphapoly-enter-positionnpx skills add chainstacklabs/polymarket-alpha-bot --skill alphapoly-enter-positiongit clone --depth 1 https://github.com/chainstacklabs/polymarket-alpha-botWrote 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/chainstacklabs/polymarket-alpha-bot/alphapoly-enter-position)<a href="https://agentmods.dev/skills/chainstacklabs/polymarket-alpha-bot/alphapoly-enter-position"><img src="https://agentmods.dev/badge/skills/chainstacklabs/polymarket-alpha-bot/alphapoly-enter-position.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.00077 | $0.00667 |
| Opus 5 | $0.00039 | $0.00333 |
| Sonnet 5 | $0.00015 | $0.00133 |
| Haiku 4.5 | $0.00008 | $0.00067 |
Grade A, and why
Entering an Alphapoly Position 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 4d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Entering an Alphapoly Position
Enter a hedged pair position (target + cover) from a detected alphapoly portfolio.
Prerequisites
- Backend running on
http://localhost:8000 - Wallet unlocked — check
GET /wallet/statusfor"unlocked": true; unlock viaPOST /wallet/unlockwith{"password": "<password>"} - Deposit wallet ready — trades sign as sigtype-3 through a per-user deposit wallet, so
GET /wallet/statusmust show"relayer_set": trueand"deposit_wallet_deployed": true. If not: attach the relayer key (POST /wallet/set-relayer), then deploy (POST /wallet/deploy-deposit-wallet). Without this,buy-pairfails at order placement. - Sufficient pUSD in the deposit wallet — the balance must sit in the deposit wallet (
deposit_wallet_addressfrom status), not the signer EOA; total cost isamount_per_position * 2. The relayer pays gas, so no POL is needed.
7-Step Flow
- List portfolios —
GET /data/portfolios; notepair_id, market IDs, and position sides - Pick a pair — select by
pair_id - Set amount — choose
amount_per_positionin pUSD - Estimate (required) —
POST /trading/buy-pair/estimate; show result to user; stop ifsufficient_balance: false - Confirm — require explicit user approval before proceeding
- Execute —
POST /trading/buy-pair; checksuccess: trueon both legs; surface anywarnings - Record — position is recorded automatically on success; manual
POST /positionsonly needed for imports
For full request/response schemas, see api-reference.md.
Safety Rules
These trades involve real pUSD on Polygon — transactions are irreversible once submitted on-chain. The estimate step is the only chance to catch problems before money moves.
- Always run
/trading/buy-pair/estimatebefore/trading/buy-pair— the estimate reveals actual costs, slippage, and balance issues before committing funds - Never execute without explicit user confirmation — the user needs to see the estimate and agree to the cost
- Never proceed if
sufficient_balance: false— the transaction will fail on-chain and may leave partial state - If
warningsare non-empty after execution, surface them — the user may hold unwanted tokens that need selling viaGET /positions skip_clob_sell: trueonly when the user explicitly requests it
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.
- 4d ago First seen · 38 lines · 77 tokens per session scan A 9a473be7bee7
Entering an Alphapoly Position is a skill published in the GitHub repository chainstacklabs/polymarket-alpha-bot (174 stars, last pushed 29d ago), licensed Apache-2.0. It adds 77 tokens to every session and 667 once invoked, about $0.0004 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
polymarket-profile
Polymarket address profiler — input any 0x address, get a complete trading profile with PnL, win rate, positions, category breakdown, and top trades. All data from public APIs, no local database needed.
polymarket
Trade on Polymarket prediction markets (CLOB V2) from a Privy EOA wallet. Search markets, place/cancel orders, manage positions. No private key handling. Use when the user wants to bet on event outcomes (e.g. "buy YES at 0.65 on the ceasefire market", "what are my open positions", "close my Trump bet").
polymarket-plugin
Trade prediction markets on Polymarket - buy outcome tokens (YES/NO and categorical markets), check positions, list markets, manage orders, redeem winning tokens, and deposit funds on Polygon. Trigger phrases: buy polymarket shares, sell polymarket position, check my polymarket positions, list polymarket markets, get…
polymarket
Query Polymarket: markets, prices, orderbooks, history.
hyperliquid
Use when backtesting, deploying, funding, or debugging a live trading strategy on Hyperliquid through the Superior Trade API — writing Freqtrade configs and strategy code, running backtest sweeps, checking wallet balances, depositing USDC, trading HIP-3 stock/commodity perps, or diagnosing a deployment that will not…
basis-arb
Use when the user asks for spot-perp basis trade, basis arbitrage, cash-and-carry, perp discount, or any setup that reads the spot–perp basis as a positioning signal. Long-perp leg only — pure two-leg basis arb requires a paired spot short (or long) which Freqtrade can't run cleanly. The strategy below captures the…