dry-run-a-risky-change SKILL.md skillA
dry-run-a-risky-change from different-ai/openwork is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add different-ai/openwork/dry-run-a-risky-change@git:20261027.7fb680fPins git:20261027.7fb680f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- different-ai/openwork
- Path
.opencode/skills/dry-run-a-risky-change/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261027.7fb680f, committed Oct 27, 2026
- First version recorded
- Oct 27, 2026
- Size
- 7,500 bytes
- Repository stars
- 24,350
- License
- a license file GitHub does not identify
Billing, plans, seats, permissions, access rules, auth, flag removals or data migrations that could lock real organizations out or change what they pay. Use before merging or deploying such a change to see exactly which production organizations it affects, prove the UI on production-shaped data, and only with explicit approval test against a PlanetScale copy of real data.
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
# Dry-run a risky change
Tests prove the rule you wrote. They do not tell you which real organizations
the rule changes. Before a risky change ships, answer three questions in order
and stop at the first level that answers them:
1. **Who changes?** Every production organization whose outcome differs
before vs after (blocked, unblocked, billed differently, loses access).
2. **Does it look right to them?** The real screens on organizations shaped
like the affected ones.
3. **Does it behave right on real data?** Only when 1 and 2 cannot answer it.
Confidentiality (AGENTS.md, hard rule): production names, ids, emails and
counts stay in chat. Never put them in a branch, commit, fixture, screenshot,
PR or issue. Describe affected organizations generically ("one grandfathered
org with ~30 SSO users").
## Level 1: read-only production dry run (always)
Run the new rule against production inputs without writing anything.
1. Write the new rule's inputs as the smallest set of columns (plan metadata,
member counts, subscription status, feature overrides). Express the rule
either as SQL or by feeding query results into the PR's pure function.
…Read the whole file at its exact version.
How to install
mdr add different-ai/openwork/dry-run-a-risky-change@sha256:145ec653d43360bdThe line at the top of this page pins the label git:20261027.7fb680f, 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.
[](https://markdownregistry.com/a/art_qlviejprqtutoqlj)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, all committed on Oct 27, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.7fb680f latest | 2026-10-27 | 7fb680f | 7,500 B | A | view · diff |
| git:20261027.7dadfbc | 2026-10-27 | 7dadfbc | 6,830 B | A | view · diff |
| git:20261027.48e8108 | 2026-10-27 | 48e8108 | 6,682 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7500 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
different-ai/openwork · 24,350 stars · license a license file GitHub does not identify · pushed 2026-10-31 · branch dev
API
GET https://markdownregistry.com/api/v1/artifacts/art_qlviejprqtutoqlj GET https://markdownregistry.com/api/v1/resolve?ref=different-ai/openwork/dry-run-a-risky-change GET https://markdownregistry.com/api/v1/blob/145ec653d43360bd6bf702eff786f10bdcfeeecda8ae58de9b058ad50244833b
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.