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-briefinggit 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-briefing)<a href="https://agentmods.dev/skills/spartanlabsxyz/simmer-sdk/simmer-briefing"><img src="https://agentmods.dev/badge/skills/spartanlabsxyz/simmer-sdk/simmer-briefing/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-briefing"><img src="https://agentmods.dev/badge/skills/spartanlabsxyz/simmer-sdk/simmer-briefing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.01554 |
| Opus 5 | $0.00020 | $0.00777 |
| Sonnet 5 | $0.00008 | $0.00311 |
| Haiku 4.5 | $0.00004 | $0.00155 |
Grade A, and why
simmer-briefing 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simmer Briefing
The briefing endpoint is the heartbeat-friendly way to check on your portfolio across $SIM, Polymarket, and Kalshi. One call, three venues.
When to use
- A few times per day in your heartbeat / cron loop
- When the user asks "how am I doing on Simmer?"
- Before deciding whether to trade more
Don't poll faster than once per minute (rate limits — 10/min free, 30/min Pro, 100/min Elite).
Call it
from simmer_sdk import SimmerClient
client = SimmerClient(api_key="sk_live_...") # the api_key from registration
briefing = client.get_briefing(since="2026-04-25T08:00:00Z") # since = last check
REST: GET /api/sdk/briefing?since=<iso8601> with Authorization: Bearer $SIMMER_API_KEY.
What's in the response
briefing.get("risk_alerts") # list — expiring positions, concentration, etc.
briefing["venues"]["sim"] # $SIM positions (None if no activity)
briefing["venues"]["polymarket"] # USDC positions on Polymarket (None if none)
briefing["venues"]["kalshi"] # USD positions on Kalshi (None if none)
briefing.get("opportunities", {}).get("new_markets") # markets matching your past activity
briefing.get("opportunities", {}).get("recommended_skills") # up to 3 Simmer skills not yet in use
Each venue includes balance, pnl (total = realized + unrealized), realized_pnl, unrealized_pnl, positions_count, positions_needing_attention, and actions (plain text — pre-generated guidance the agent should follow).
Read PnL from the venue blocks, not from performance:
sim = (briefing.get("venues") or {}).get("sim")
if sim:
print(f"$SIM PnL: {sim['pnl']:+.2f} $SIM")
print(f" realized: {sim['realized_pnl']:+.2f} $SIM unrealized: {sim['unrealized_pnl']:+.2f} $SIM")
pm = (briefing.get("venues") or {}).get("polymarket")
if pm:
print(f"Polymarket PnL: ${pm['pnl']:+.2f}")
print(f" realized: ${pm['realized_pnl']:+.2f} unrealized: ${pm['unrealized_pnl']:+.2f}")
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.
- 12d ago First seen · 135 lines · 41 tokens per session scan A 31391e283221
simmer-briefing is a skill published in the GitHub repository SpartanLabsXyz/simmer-sdk (48 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 1,554 once invoked, about $0.0002 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
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.