bench-repro SKILL.md skillA

bench-repro from d-robotics/moss is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add d-robotics/moss/bench-repro@git:20260930.19b5ead

Pins git:20260930.19b5ead in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
d-robotics/moss
Path
.moss/skills/bench-repro/SKILL.md
Versions recorded
1
Latest version
git:20260930.19b5ead, committed Sep 30, 2026
Size
1,154 bytes
Repository stars
143
License
MIT

How to reproduce and grade a bench task or A/B arm for moss capability work.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Reproducing bench evidence

- Internal bench: `npm run bench -- --task <id> --samples <n> --label <label>` (provider via `MOSS_BENCH_API_KEY`, `--model`, `--base-url`; temp=0; approval=never). Results land in `bench/results/<label>/` (never committed).
- A/B: `npm run bench:ab -- <engine> --samples <n>` for `best-of-n` / `reasoning-high` / `goal-loop` / `model-routing`; the verdict json lands in `bench/results/ab-<engine>-<stamp>.json`.
- Noise discipline: compare only same-SHA runs; use `npm run bench:noise` for the noise band; a delta inside the band is not evidence.
- SWE-bench (external board): `npm run bench:swe -- --samples 2 --label <label>` produces predictions; grade with `npm run bench:swe -- --eval --label <label>`. Instance subset is locked in `bench/boards/swebench-instances.json` — never edit it mid-study.
- A baseline must be collected from a pinned build (`--dist bench/.cache/<snapshot>/dist`), not from a dirty tree.

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add d-robotics/moss/bench-repro@sha256:5e196f1ca11d4808

The line at the top of this page pins the label git:20260930.19b5ead, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_5jb2o6rnil2r6pim.svg)](https://markdownregistry.com/a/art_5jb2o6rnil2r6pim)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Sep 30, 2026.

versioncommittedcommitsizeaudit
git:20260930.19b5ead latest2026-09-30 19b5ead 1,154 BA view

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (1154 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

d-robotics/moss · 143 stars · license MIT · pushed 2026-10-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_5jb2o6rnil2r6pim
GET https://markdownregistry.com/api/v1/resolve?ref=d-robotics/moss/bench-repro
GET https://markdownregistry.com/api/v1/blob/5e196f1ca11d480828a237bc20ba2753dfd59bcf4588272a947e42766add2b16

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from d-robotics/moss

patch-discipline SKILL.md skill
d-robotics/moss · .moss/skills/patch-discipline/SKILL.md · How to make code changes in the moss repo — read-before-edit, minimal diffs, verify with real runs
git:20260930.19b5ead · audit A · 143 stars
worktree-parallel SKILL.md skill
d-robotics/moss · .moss/skills/worktree-parallel/SKILL.md · How to run writable sub-agents in isolated git worktrees and merge their lease patches
git:20260930.19b5ead · audit A · 143 stars
AGENTS.md AGENTS.md file
d-robotics/moss · AGENTS.md
git:20261011.8977a42 · audit A · 143 stars
AGENTS.md@bench/tasks/no-interaction/files AGENTS.md file
d-robotics/moss · bench/tasks/no-interaction/files/AGENTS.md
git:20260928.5ba8ff3 · audit B · 143 stars

Every file in d-robotics/moss

Browse by kind, by grade A, or by owner.