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 autoresearch-finalizegit 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/autoresearch-finalize)<a href="https://agentmods.dev/skills/spartanlabsxyz/simmer-sdk/autoresearch-finalize"><img src="https://agentmods.dev/badge/skills/spartanlabsxyz/simmer-sdk/autoresearch-finalize/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/autoresearch-finalize"><img src="https://agentmods.dev/badge/skills/spartanlabsxyz/simmer-sdk/autoresearch-finalize.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.00040 | $0.00609 |
| Opus 5 | $0.00020 | $0.00304 |
| Sonnet 5 | $0.00008 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
autoresearch-finalize 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 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.
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finalize Autoresearch
Turn a noisy autoresearch branch into clean, independent branches — one per logical change, each starting from the merge-base.
Step 1 — Analyze and propose groups
- Read
autoresearch.jsonl. Filter to kept experiments only. - Read
autoresearch.mdfor context. - Expand all short commit hashes to full hashes:
git rev-parse <short_hash> - Get the merge-base:
git merge-base HEAD main - For each kept commit, get the diff stat.
- Group kept commits into logical changesets:
- Preserve application order. Group N comes before Group N+1.
- No two groups may touch the same file. Each branch is applied to merge-base independently — overlapping files would conflict. If two groups touch the same file, merge them into one group.
- Watch for cross-file dependencies. If group 1 adds an API in
api.jsand group 2 calls it inparser.js, group 2's branch won't work in isolation. Flag dependencies. - Keep each group small and focused. One idea, one theme per group.
Present the proposed grouping:
Proposed branches (each from merge-base, independent):
1. **<description>** (commits abc1234, def5678)
Files: file1.py, file2.py
Metric: 42.3 → 38.1 (-9.9%)
2. **<description>** (commits ghi9012)
Files: config.json
Metric: 38.1 → 31.7 (-16.8%)
Wait for approval before proceeding.
Step 2 — Create branches
For each approved group:
BASE=$(git merge-base HEAD main)
git checkout -b autoresearch/final/<group-name> $BASE
git cherry-pick <commit1> <commit2> ...
If cherry-pick conflicts, resolve by taking the experiment's version (the whole point is to preserve the improvement).
Step 3 — Verify each branch
For each branch:
- Run the skill command to verify it still works
- Check that the metric improvement holds
- If it doesn't, flag it — the improvement may have depended on another group's changes
Step 4 — Report
Finalized branches:
1. autoresearch/final/<name> — <metric improvement>, ready to merge
2. autoresearch/final/<name> — <metric improvement>, depends on branch 1
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 · 67 lines · 40 tokens per session scan A 177bbcdeca58
autoresearch-finalize is a skill published in the GitHub repository SpartanLabsXyz/simmer-sdk (48 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 609 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.
shipp-sports-data
Real-time sports & events data for AI agents via Shipp. Use when the user wants live scores, schedules, or game events for NBA, NFL, NCAA Football, MLB, or Soccer — especially to power prediction market trading strategies on Polymarket or Kalshi using a MoonPay wallet.
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.