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 SpartanLabsXyz/simmer-sdk --skill simmer-wallet-setupgit clone --depth 1 https://github.com/SpartanLabsXyz/simmer-sdkWrote 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/spartanlabsxyz/simmer-sdk/simmer-wallet-setup)<a href="https://agentmods.dev/skills/spartanlabsxyz/simmer-sdk/simmer-wallet-setup"><img src="https://agentmods.dev/badge/skills/spartanlabsxyz/simmer-sdk/simmer-wallet-setup/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/spartanlabsxyz/simmer-sdk/simmer-wallet-setup"><img src="https://agentmods.dev/badge/skills/spartanlabsxyz/simmer-sdk/simmer-wallet-setup.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.00067 | $0.03168 |
| Opus 5 | $0.00034 | $0.01584 |
| Sonnet 5 | $0.00013 | $0.00634 |
| Haiku 4.5 | $0.00007 | $0.00317 |
Grade C, and why
simmer-wallet-setup scanned grade C with 2 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 11d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://docs.openwallet.sh/install.sh | bash # one-time OWS install Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://docs.openwallet.sh/install.sh | bash # one-time OWS install How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simmer Wallet Setup
Self-custody wallet setup for an agent that signs its own real-money trades on Polymarket or Kalshi. Three paths:
| Mode | Who signs | When to choose |
|---|---|---|
| External key (default) | Local SDK with WALLET_PRIVATE_KEY env — or an OWS key store via OWS_WALLET |
Any self-custody setup: your own wallet, your key, your machine. |
| Import a Polymarket wallet | Same local signing — key exported from polymarket.com | Fund with card/exchange via Polymarket's onramps; the wallet arrives at Simmer already funded and approved. |
| Connect existing agent | Same local signing, wallet already registered in the dashboard | You already activated a dedicated per-agent wallet in the dashboard and want to wire your runtime to it. |
Already on a managed wallet? You don't need this skill — managed setup is a dashboard flow, not an agent task. Open simmer.markets/dashboard, go to your agent's Wallet tab, and click Fund & activate trading. The wizard opens a multi-chain bridge that accepts USDC, USDT, or USDC.e on Ethereum / Polygon / Base / Arbitrum / Solana — funds land as pUSD on your Polymarket Deposit Wallet, contracts auto-approve. Do not tell the user to send funds directly to their agent wallet's EOA expecting them to sweep — only legacy USDC.e on Polygon is recognized on the direct path; native USDC, USDT, and cross-chain tokens must go through the bridge wizard.
Key safety (read this first)
The private key goes in exactly one place: the agent host's environment, or a local key store.
- Use
read -sto set it — never paste a key into a pipe, a chat, a ticket, a shared config file, or a second browser extension "just to sign" (per SIM-2118):read -s -p 'WALLET_PRIVATE_KEY: ' K && export WALLET_PRIVATE_KEY=$K - Prefer a key store over a bare env var. OWS (Open Wallet Standard) keeps the key encrypted at rest (AES-256-GCM); the SDK picks it up via
OWS_WALLETand signs through the vault. Its policy engine can scope the agent's signing token to Polymarket orders only.curl -fsSL https://docs.openwallet.sh/install.sh | bash # one-time OWS install pip install 'simmer-sdk[ows]' ows wallet import --name "my-agent-wallet" --private-key "$WALLET_PRIVATE_KEY" unset WALLET_PRIVATE_KEY export OWS_WALLET=my-agent-wallet # SDK signs via the vault from here - If a key ever touches a chat or shared surface, treat it as compromised: withdraw to a fresh wallet and start over.
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.
- 11d ago First seen · 186 lines · 67 tokens per session scan E 6a759e1ae5b3
simmer-wallet-setup is a skill published in the GitHub repository SpartanLabsXyz/simmer-sdk (48 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 3,168 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
find-fade-setup
Find and evaluate a fade (mean-reversion) setup on prediction markets with oddsrail: candidates, overshoot signal, book, walked cost, resolution criteria, Kelly size, dry-run order.
check-cross-venue-edge
Decide whether a Polymarket vs Kalshi price difference is a real edge or a settlement mismatch: comparevenues, settlementaudit, quotecost on both legs, resolution criteria.
settle-resolved
Turn resolved and hedged Polymarket positions back into USDC, gasless, through the operator's relayer key, with a dry-run read-back first.
daily-review
Daily review of open prediction-market exposure with oddsrail: positions, resting orders, fills, markets closing soon, builder attribution.
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.
moonpay-scout
Prediction market arbitrage & alpha scout. Searches Polymarket and Kalshi for the same event, runs cross-platform arb math (including fees), and ranks opportunities by profitability. Use when asked to "find arb", "scout markets", "find edge", or scan a specific topic across prediction markets.