What is Exiting an Alphapoly Position?

A workflow for selling or merging tokens from an open Alphapoly trading position. It covers choosing the correct action, confirming it, executing it, and checking the result.

Use it to fully close a position, sell one token side, clear leftover tokens, merge resolved outcomes, retry pending positions, and verify completion.

It helps avoid using the wrong exit action for the position’s state and requires approval before a sale or merge.

How chainstacklabs/polymarket-alpha-bot configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to chainstacklabs/polymarket-alpha-bot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/chainstacklabs/polymarket-alpha-bot/main/.claude/skills/alphapoly-exit-position/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/chainstacklabs/polymarket-alpha-bot

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/chainstacklabs/polymarket-alpha-bot/alphapoly-exit-position/github.svg)](https://agentmods.dev/skills/chainstacklabs/polymarket-alpha-bot/alphapoly-exit-position)

Your own site

<a href="https://agentmods.dev/skills/chainstacklabs/polymarket-alpha-bot/alphapoly-exit-position"><img src="https://agentmods.dev/badge/skills/chainstacklabs/polymarket-alpha-bot/alphapoly-exit-position/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/chainstacklabs/polymarket-alpha-bot/alphapoly-exit-position"><img src="https://agentmods.dev/badge/skills/chainstacklabs/polymarket-alpha-bot/alphapoly-exit-position.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.1	$0.00078	$0.00710
Opus 5.5	$0.00031	$0.00284
Sonnet 5.5	$0.00016	$0.00142
Haiku 4.5	$0.00008	$0.00071

Measured 2mo ago against content hash 3f67b20ce210, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Exiting 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 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.

.claude/skills/alphapoly-exit-position/SKILL.md · 87 lines

How it starts

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

Exiting an Alphapoly Position

Prerequisites

Backend running on http://localhost:8000
Wallet unlocked (action endpoints return HTTP 401 if not)

Flow

List positions — GET /positions (or ?state=active to filter)
Pick a position — note the position_id
Choose action based on state:

Situation	Action
Fully close a position	Exit — orchestrated merge + sell (preferred)
Sell one specific side	Sell — `token_type: "wanted"`
Clear failed entry leftovers	Sell — `token_type: "unwanted"`
Market resolved, hold both outcomes	Merge
State is `pending`	Retry

Confirm — require explicit user approval before executing any sell or merge
Execute — see quick reference below
Verify — re-fetch position; full exit shows state: "complete"

Quick Reference

# Fully exit (orchestrated merge + sell) — preferred
POST /positions/{id}/exit
{"slippage": 10}

# Sell a side
POST /positions/{id}/sell
{"side": "target", "token_type": "wanted"}

# Merge resolved pair
POST /positions/{id}/merge
{"side": "target"}

# Retry pending
POST /positions/{id}/retry

# Check result
GET /positions/{id}

token_type Explained

When entering, the system splits pUSD into YES+NO tokens and sells the side you don't want via CLOB to recover partial cost.

"wanted" — the token you hold as your position (normal exit)
"unwanted" — residual from a failed or partial entry sell (cleanup)

Typical Exit Flow

GET  /positions                          # find position_id
POST /positions/{id}/sell                # {"side":"target","token_type":"wanted"}
POST /positions/{id}/sell                # {"side":"cover","token_type":"wanted"}
GET  /positions/{id}                     # confirm state == "complete"

If unwanted balances remain after entry: POST /positions/{id}/retry

If market resolved and holding both outcomes:

POST /positions/{id}/merge   # {"side":"target"}
POST /positions/{id}/merge   # {"side":"cover"}

Read the full file on GitHub · 87 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.

api-reference.md 3.0 KB

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.

2mo ago First seen · 87 lines · 78 tokens per session scan A 3f67b20ce210

Subscribe to this mod's changes

Exiting an Alphapoly Position is a skill published in the GitHub repository chainstacklabs/polymarket-alpha-bot (184 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 78 tokens to every session and 710 once invoked, about $0.0003 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-30.

Finance and fintech Web3 and blockchain polymarket prediction trading

Exiting an Alphapoly Position next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
Exiting an Alphapoly Positionchainstacklabs/polymarket-alpha-bot	Skill	184	3mo ago	Apache-2.0	A	78	Claude Code
polymarket-profilerunesleo/polymarket-toolkit	Skill	203	3d ago	MIT	A	51	Claude Code
moonpay-prediction-marketmoonpay/skills	Skill	112	17d ago	MIT	A	37	Claude Code
polymarketStarchild-ai-agent/official-skills	Skill	32	7d ago	none	A	84	Claude Code, Codex
moonpay-fund-polymarketmoonpay/skills	Skill	112	17d ago	MIT	D	30	Claude Code
polymarket-pluginokx/plugin-store	Skill	12	1mo ago	MIT	D	304	Claude Code
token-unlock-treasuryHKUDS/Vibe-Trading	Skill	38k	yesterday	MIT	A	42	Claude Code, Codex

polymarket-alpha-bot: Skill for Claude Code