AGENTS.md, a new skill, a different reasoning setting. Stet tells you which
changes are safe to keep. It replays your repository’s real accepted work under
the proposed change and returns a scoped decision. Your agent runs Stet on your
behalf; you set the question, approve the spend, and make the call.
Find your next answer
Is my AGENTS.md change helping?
Compare current and proposed instructions on the same retained tasks.
Improve my AGENTS.md
Iterate one instruction lever at a time with a bounded stop rule.
Is this skill helping?
Test a skill against an appropriate absent or committed baseline.
Which model or reasoning effort should I use?
Compare configurations on the same repository task slice.
The loop
Accepted repository work becomes replayable tasks. Stet runs a baseline and a candidate against the same task slice, evaluates their patches with tests and graders, and writes a Trial Result with one scoped recommendation.Why trust the result
- It measures your repository’s real merged work, not synthetic benchmarks.
- It is local-first: your repository, patches, and evaluation evidence stay on your machine.
- The evidence is produced independently of the agent whose change is under test.
- It fails closed: weak, stale, or contaminated evidence blocks a strong claim.
- Every decision comes with a machine-readable receipt.
Example Trial Result
An example from a model comparison on 28 paired Zod tasks: Opus 4.6 versus Opus 4.7, both at high reasoning.PROMOTE candidate Opus 4.7, high confidence, for this recorded
harness and task corpus.
Opus 4.7 showed higher means on seven of the eight craft dimensions; simplicity
dipped slightly. The scope and evidence limits are part of the result:
- Historical April 2026 result, scoped to this 28-task Zod corpus and recorded harness.
- The legacy report predates Stet’s current calibration and claim-readiness fields.
Machine-readable receipt
Machine-readable receipt