scope-confirmed-changes SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.
scope-confirmed-changes from theonly1me/shadowclone is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add theonly1me/shadowclone/scope-confirmed-changes@git:20261019.61ac16ePins git:20261019.61ac16e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- theonly1me/shadowclone
- Path
.agents/skills/scope-confirmed-changes/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261019.61ac16e, committed Oct 19, 2026
- First version recorded
- Oct 9, 2026
- Size
- 5,062 bytes
- Repository stars
- 21
- License
- MIT
Use when fixing a bug, a regression, or a confirmed review finding. Also use it when the user says "fix this bug", "it is broken", or "keep the change small". Reproduces the issue before any fix, with a test, a real command, or the real interface. After the fix, the same reproduction must pass. Keeps the change to confirmed, reachable behavior. Not for checking review comments before a fix (use `verify-review-findings`).
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
# Scope Confirmed Changes ## Use when You fix a bug, a regression, or a review finding that you confirmed. Only a reproduction proves that a bug is real. Only the same reproduction after the fix proves that the fix works. ## Gates 1. Did you reproduce the issue before you changed code, with a test, a real command, or the real interface? If the fix already exists, a test that fails when you undo the smallest part of the fix counts as the reproduction. 2. After the fix, does the same reproduction show the expected result? 3. If you could not reproduce the issue, did you label the cause as inferred, with the data and code that support it? 4. Does each changed line serve the fix, or a test or check that the fix needs? 5. Do all checks that passed before your change still pass? 6. If an approach caused a new regression, did you remove it instead of adding a second fix on top? ## Process …
Read the whole file at its exact version.
How to install
mdr add theonly1me/shadowclone/scope-confirmed-changes@sha256:8eb18f10d932c672The line at the top of this page pins the label git:20261019.61ac16e, 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_ov56blpsglorga4a)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Oct 9, 2026 and Oct 19, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.61ac16e latest | 2026-10-19 | 61ac16e | 5,062 B | A | view · diff |
| git:20261018.7be4fab | 2026-10-18 | 7be4fab | 4,052 B | A | view · diff |
| git:20261009.95ca1ef | 2026-10-09 | 95ca1ef | 4,082 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 (5062 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
theonly1me/shadowclone · 21 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ov56blpsglorga4a GET https://markdownregistry.com/api/v1/resolve?ref=theonly1me/shadowclone/scope-confirmed-changes GET https://markdownregistry.com/api/v1/blob/8eb18f10d932c672d2989f8df7e6abc0b9bdc9b854d62fe84bcb121711d1ba79
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 theonly1me/shadowclone
Every file in theonly1me/shadowclone