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 hmesutozsoy/oddsrail --skill settle-resolvedgit clone --depth 1 https://github.com/hmesutozsoy/oddsrailWrote 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/hmesutozsoy/oddsrail/settle-resolved)<a href="https://agentmods.dev/skills/hmesutozsoy/oddsrail/settle-resolved"><img src="https://agentmods.dev/badge/skills/hmesutozsoy/oddsrail/settle-resolved/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/hmesutozsoy/oddsrail/settle-resolved"><img src="https://agentmods.dev/badge/skills/hmesutozsoy/oddsrail/settle-resolved.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.00038 | $0.00293 |
| Opus 5.5 | $0.00015 | $0.00117 |
| Sonnet 5.5 | $0.00008 | $0.00059 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
settle-resolved 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 today.
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
settle resolved
Use the tools of the oddsrail MCP server (install: pip install oddsrail, then configure your MCP client with local stdio command oddsrail and no arguments). Prices are implied probabilities in (0,1). Trading tools are dry-run unless the operator has set ODDSRAIL_DRY_RUN=0; never assume an order was placed without checking the dry_run field of the result.
Settle whatever can be settled on the operator's Polymarket account.
- server_info(): confirm relayer_key_configured is true and note dry_run.
- redeemable_positions(): two lists, redeemable (resolved winners) and mergeable (both sides held).
- For each redeemable entry: redeem_positions(condition_id=...). For each mergeable entry: merge_positions(condition_id=..., amount="max"). In dry-run these return the intent; read each back before the operator sets ODDSRAIL_DRY_RUN=0.
- After live submissions: report transaction ids and outcomes, then my_positions() to confirm the balances moved.
Do not resubmit anything whose outcome is "unknown"; report it instead.
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.
- today Changed c1922a16925d
- 11d ago Changed 931eb9eecd3b
- 1mo ago First seen · 23 lines · 38 tokens per session scan A 4a439096766e
settle-resolved is a skill published in the GitHub repository hmesutozsoy/oddsrail (1 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 293 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
polymarket-copytrading
Mirror Polymarket whale wallets, inspect wallet positions, follow specific trader addresses, or paper-trade copytrading with $SIM before using real money. Polling mode is free; Reactor mode is Pro for event-driven real-time mirroring via Simmer's on-chain signal infrastructure.
polymarket-weather-trader
Trade Polymarket temperature markets from NOAA and Open-Meteo forecasts via the Simmer API. Use to run or configure a weather strategy, or to check the forecast a market resolves on.
polymarket-btc-up-down-trader
Trade Polymarket BTC daily and weekly UP/DOWN markets with empirically-anchored exit discipline. Enters on CEX momentum divergence; exits automatically on time cap, volume spike, or target capture. Use when the user wants to trade BTC direction markets (hours/days duration), not fast 5-minute markets.
polymarket-fast-loop
Trade Polymarket 5-minute and 15-minute crypto sprint markets, automate short-term prediction trading, use CEX momentum or custom signals, or monitor sprint-market positions. Default signal is Binance BTC/USDT klines.
polymarket-soccer-shock-ladder
Fade sharp in-play price shocks on Polymarket soccer markets with a laddered limit-buy strategy (Roan's FIFA-quant framework). Pro skill. Currently scoped to 2026 World Cup markets. Simmer's server detects shocks in real time and emits pre-sized signals; this skill places the recovery ladder and manages the exit.
nansen-copytrader-overlay
Rank Polymarket copytrading leaders using Nansen as a data layer — pnl-by-market for the target market is the primary signal, address-summary/pnl-by-address is a secondary, credit-guarded refinement. Includes an experimental (dry-run only) live insider scan. Use when Simmer needs to re-rank or filter a leader list…