patch-discipline SKILL.md skillA

patch-discipline 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/patch-discipline@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/patch-discipline/SKILL.md
Versions recorded
1
Latest version
git:20260930.19b5ead, committed Sep 30, 2026
Size
1,057 bytes
Repository stars
143
License
MIT

How to make code changes in the moss repo — read-before-edit, minimal diffs, verify with real runs.

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

# Patch discipline for moss

1. Read the real source before editing. Never guess behavior from file names.
2. Make the minimal change that fixes the problem. Match surrounding style; do not refactor neighbors in the same patch.
3. Every user-facing success message must come from a real probe, exit code, or post-condition — never a fixed string.
4. All subprocesses go through `runProcess` / `spawnProcess` from `src/utils/run-process.ts`; tool paths must not use execFileSync/execSync.
5. New tools must declare `metadata.sideEffectClass` (readonly vs mutating drives approval).
6. After a logic change: `npm run build` then run the touched spec (`npm run test:filter -- --filter <module>`). A bug fix needs a red-then-green regression spec.
7. Errors crossing tool/provider/CLI boundaries become `MossError` with the original cause preserved.

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add d-robotics/moss/patch-discipline@sha256:0d2454b45f192294

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_zsi6jv6hm3x5xukp.svg)](https://markdownregistry.com/a/art_zsi6jv6hm3x5xukp)

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,057 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 (1057 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_zsi6jv6hm3x5xukp
GET https://markdownregistry.com/api/v1/resolve?ref=d-robotics/moss/patch-discipline
GET https://markdownregistry.com/api/v1/blob/0d2454b45f1922948c162acb45fbdfad90af75ea6717884d7a438d5eb0240997

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

bench-repro SKILL.md skill
d-robotics/moss · .moss/skills/bench-repro/SKILL.md · How to reproduce and grade a bench task or A/B arm for moss capability work
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.