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 agentmods add instructions/2389-research/simmer/claude-mdgit clone --depth 1 https://github.com/2389-research/simmerWrote 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/instructions/2389-research/simmer/claude-md)<a href="https://agentmods.dev/instructions/2389-research/simmer/claude-md"><img src="https://agentmods.dev/badge/instructions/2389-research/simmer/claude-md.svg" alt="Measured on agentmods" 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.01220 | $0.01220 |
| Opus 5 | $0.00610 | $0.00610 |
| Sonnet 5 | $0.00244 | $0.00244 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
simmer CLAUDE.md 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 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.
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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simmer Plugin
Overview
Simmer is an iterative refinement skill. It takes any artifact — a single file, a workspace of multiple files, a pipeline, a configuration — and hones it repeatedly against user-defined criteria. Evaluation can be subjective (judge-based), objective (runnable script), or hybrid (both).
Skills Included
| Skill | Triggers | Description |
|---|---|---|
simmer |
"simmer this", "refine this", "hone this", "iterate on this", "optimize this pipeline" | Orchestrator: setup → loop → output |
Subskills (invoked by orchestrator)
| Subskill | Role |
|---|---|
simmer:simmer-setup |
Identify artifact (file or workspace), elicit criteria, determine evaluation method, produce setup brief |
simmer:simmer-generator |
Produce improved candidate from current + ASI feedback + background context |
simmer:simmer-judge |
Score candidate 1-10 per criterion (with optional evaluator output), produce ASI |
simmer:simmer-judge-board |
Multi-judge panel with deliberation — drop-in replacement for simmer-judge when JUDGE_MODE is board |
simmer:simmer-reflect |
Record trajectory, track best-so-far, pass ASI forward |
Flow
"Simmer this" / "Refine this" / "Optimize this pipeline"
↓
Setup (identify artifact + criteria + evaluation method)
↓
Iteration 0: Evaluate the seed
↓
Loop N times:
Generate (address ASI) → Evaluate (run evaluator if present) → Judge (score + new ASI) → Reflect (record)
↓
Output best candidate + trajectory
Key Design Decisions
Context discipline: Generator doesn't see scores (avoids optimizing for numbers). Judge doesn't see intermediate scores (avoids anchoring). Reflect is the only subskill that sees the full trajectory.
Seed calibration: Judge receives the seed artifact + iteration-0 scores on every iteration as a fixed calibration reference. Can score above or below the seed. This compresses score variance across runs.
ASI (Actionable Side Information): Judge identifies the highest-leverage direction each round. For single-file targets, this is a single focused fix. For workspace targets, this is a single strategic direction that may involve coordinated changes across multiple files. Focused directional improvement compounds better than scattered edits.
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 First seen · 125 lines · 1,220 tokens per session scan A d094a50c64f4
simmer CLAUDE.md is an instructions file published in the GitHub repository 2389-research/simmer (14 stars, last pushed 2mo ago), licensed MIT. It adds 1,220 tokens to every session, about $0.0061 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 instructions, from other repositories
autoresearch AGENTS.md
Instructions for uditgoenka/autoresearch, covering agents.md — autoresearch, what is autoresearch?, installation, claude code (plugin) and codex (plugin).
app-privacy-policy-generator AGENTS.md
AGENTS.md instructions for nisrulz/app-privacy-policy-generator, covering agents.md, project overview, source layout, build and code conventions.
kkRepo AGENTS.md
AGENTS.md instructions for klboke/kkRepo, covering kkrepo agent 指南, 产品目标, 强制开发规则, 兼容性工作流 and 构建与测试注意事项.
kkRepo copilot-instructions.md
Copilot instructions for klboke/kkRepo, covering kkrepo copilot instructions, engineering rules, build and test, compatibility workflow and review focus.
kkRepo protocol-compat.instructions.md
Instructions for klboke/kkRepo, a project described as: kkRepo is a Nexus-compatible, self-hosted artifact repository for Maven, npm, PyPI, Go, Helm, NuGet, Cargo/Rust, Dart/Pub, Docker/OCI, RubyGems, and Yum artifacts. It supports one-click migration from Nexus to kkRepo.
kkRepo java-server.instructions.md
Instructions for klboke/kkRepo, a project described as: kkRepo is a Nexus-compatible, self-hosted artifact repository for Maven, npm, PyPI, Go, Helm, NuGet, Cargo/Rust, Dart/Pub, Docker/OCI, RubyGems, and Yum artifacts. It supports one-click migration from Nexus to kkRepo.