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-skill-buildergit 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-skill-builder)<a href="https://agentmods.dev/skills/spartanlabsxyz/simmer-sdk/simmer-skill-builder"><img src="https://agentmods.dev/badge/skills/spartanlabsxyz/simmer-sdk/simmer-skill-builder/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-skill-builder"><img src="https://agentmods.dev/badge/skills/spartanlabsxyz/simmer-sdk/simmer-skill-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 281 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 297 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 362 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 387 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 316 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 321 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00086 | $0.06512 |
| Opus 5 | $0.00043 | $0.03256 |
| Sonnet 5 | $0.00017 | $0.01302 |
| Haiku 4.5 | $0.00009 | $0.00651 |
Grade A, and why
simmer-skill-builder scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
6. **Use stdlib only** for HTTP (urllib). Don't add `requests`, `httpx`, or `aiohttp` as dependencies unless your human specifically needs them. The only pip dependency should be `simmer-sdk`. How it starts
The opening of the file, as written. The whole thing — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simmer Skill Builder
Generate complete, runnable Simmer trading skills from a strategy description.
You are building an OpenClaw skill that trades prediction markets through the Simmer SDK. The skill you generate will be installed into your skill library and run by you — it must be a complete, self-contained folder that works out of the box.
Use this skill when a human has a rough trading idea, a bounty brief, or a strategy thread and wants a deterministic skill they can validate, publish, and run. The best output is not just a clever prompt: it is a folder with bounded trading logic, explicit config, dry-run defaults, and enough docs for another builder to remix.
Workflow
Step 1: Intake and Triage
1a. Detect input type
Your human's input falls into one of two modes:
- Conversational (short description, thesis statement, "build me a bot that...") → go to 1b
- Pasted post / campaign brief (long text >500 chars, contains code blocks, threshold numbers, or reads like an X thread, blog post, bounty, or World Cup strategy idea) → go to 1c
1b. Conversational intake
Ask your human to clarify until you understand these five parameters:
- Signal — What data drives the decision? (external API, market price, on-chain data, LLM probability estimate, timing, etc.)
- Entry logic — When to buy? (price threshold, signal divergence, edge %, timing window, etc.)
- Exit logic — When to sell? (take profit, time-based, signal reversal, or rely on auto-risk monitors — if unclear, default to auto-risk monitors but confirm with human)
- Market selection — Which markets? (by tag, keyword, category, venue, volume filter, resolution window, or discovery logic)
- Position sizing — Fixed amount or smart sizing? What Kelly fraction? What bankroll-% cap? What order type (market or limit)?
1c. From-post extraction
When the human pastes a strategy post or campaign brief, extract — don't ask first. The post often contains the strategy shape already. Ask follow-ups only after you have separated what is explicit from what is missing.
What ships with it
9 files 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.
- clawhub.json 243 B
- references/example-llm-oracle.md 10 KB
- references/example-mert-sniper.md 3.4 KB
- references/example-weather-trader.md 3.7 KB
- references/fixture-lunar-quant.md 2.9 KB
- references/simmer-api.md 12 KB
- references/skill-template.md 17 KB
- scripts/status.py 4.0 KB runs code
- scripts/validate_skill.py 6.9 KB runs code
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.
- 5d ago Changed 7410466a24f4
- 11d ago First seen · 390 lines · 86 tokens per session scan A eb382544ecad
simmer-skill-builder is a skill published in the GitHub repository SpartanLabsXyz/simmer-sdk (48 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 6,512 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (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
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.
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
Query Polymarket: markets, prices, orderbooks, history.