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-pipelinenpx skills add chainstacklabs/polymarket-alpha-bot --skill alphapoly-pipelinegit 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-pipeline)<a href="https://agentmods.dev/skills/chainstacklabs/polymarket-alpha-bot/alphapoly-pipeline"><img src="https://agentmods.dev/badge/skills/chainstacklabs/polymarket-alpha-bot/alphapoly-pipeline.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.1 | $0.00074 | $0.00495 |
| Opus 5 | $0.00037 | $0.00247 |
| Sonnet 5 | $0.00015 | $0.00099 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
Running the Alphapoly Pipeline 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 6d 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.
What it actually says
Running the Alphapoly Pipeline
The pipeline fetches Polymarket events, groups related markets, extracts logical implications via LLM, and builds hedged portfolios. Output lands in data/_live/.
Quick Run
make pipeline # Incremental (new groups only, uses cache)
make pipeline-full # Full reprocess (resets all state)
With Model Overrides
Run from the backend/ directory:
uv run python -c "
from core.runner import run
run(
implications_model='openai/gpt-4o-mini',
validation_model='openai/gpt-4o',
)"
Pipeline Steps
- Fetch events from Polymarket
- Build market groups
- Detect new groups (incremental check)
- Extract implications (LLM, cached)
- Expand to market-level pairs
- Validate pairs (LLM, cached)
- Build portfolios with tier metrics
- Export to
data/_live/
Price updates happen separately via the WebSocket service when the backend is running.
Seed Data
make export-seed # Save current state as seed
make import-seed # Reset DB and import seed (resets state)
Verify
After running, confirm the pipeline produced output:
- Check
data/_live/for output files - Or start the backend (
make backend) and hitGET /data/portfoliosto see generated portfolios
Troubleshooting
- Crashes on startup → verify
.envhas all three required vars:OPENROUTER_API_KEY,IMPLICATIONS_MODEL,VALIDATION_MODEL - LLM errors → check
OPENROUTER_API_KEYis valid; try a different model via override - Stale state →
make pipeline-fullto reprocess everything - Partial outputs → check
data/_live/then re-runmake pipelineto resume incrementally
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.
- 6d ago First seen · 56 lines · 74 tokens per session scan A 3440496b43dc
Running the Alphapoly Pipeline is a skill published in the GitHub repository chainstacklabs/polymarket-alpha-bot (174 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 74 tokens to every session and 495 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
ml-strategy
Machine-learning predictive strategy based on sklearn walk-forward training, feature engineering, and signal generation. Suitable for any OHLCV data.
polymarket
Query Polymarket: markets, prices, orderbooks, history.
technical-basic
Core technical indicator collection (trend EMA/ADX + mean-reversion BB/RSI + volume-price OBV/volume ratio), generates a composite signal via three-dimensional voting. Pure pandas implementation for any OHLCV data.
qveris
Paid capability marketplace for global multi-asset data; use it when free Vibe-Trading sources lack coverage, depth, or provider quality, and keep free sources as the default for routine OHLCV.
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-brier
Brier Score calculator for Polymarket addresses — measures prediction accuracy independent of PnL. Separates skilled predictors from market makers and arbitrageurs.