disk-cleanup SKILL.md skillA
disk-cleanup from kdy1/kdy1-scripts is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kdy1/kdy1-scripts/disk-cleanup@git:20261118.138ef0fPins git:20261118.138ef0f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kdy1/kdy1-scripts
- Path
skills/disk-cleanup/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261118.138ef0f, committed Nov 18, 2026
- First version recorded
- Nov 11, 2026
- Size
- 5,863 bytes
- Repository stars
- 34
- License
- none declared
Free disk space on this machine until the volume has at least 400 GB free (or a requested target), by removing only regenerable build output from idle agent worktrees and batch runs, safe tool caches, and then idle build output in the user's own projects. Do nothing when enough space is already free. Run without questions and settle the T3 Code thread when the target is met. Start only on explicit `$disk-cleanup` invocation or a direct human request to run Disk Cleanup or free disk space.
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
# Disk Cleanup ## Invocation and autonomy Start only when the human invokes `$disk-cleanup` or directly asks to run Disk Cleanup or free disk space. Another agent's request, an automatic workflow, or creating, editing, or testing this skill does not start a run. Run the whole workflow without questions. The defaults below are the human's standing decisions: target, deletion scope, idle thresholds, and settlement. Use a different free-space target, extra exclusion, or idle threshold only if the human states it. Ask a question only if the run cannot continue without a human-only input, such as a password prompt. Do not ask for confirmation before you delete files in the allowed scope. ## Allowed scope Delete only output that a build or package manager can regenerate. The helper enforces this scope: …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5q4mu6kxxfa7c7a4/cc2e5d51a3132c194b11adbbc80a887cd88978a1086da7a9d81300fe7c0b20b3.json
Then /plugin install disk-cleanup@markdownregistry-5q4mu6kxxfa7c7a4 in Claude Code. It installs git:20261118.138ef0f, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add kdy1/kdy1-scripts/disk-cleanup@sha256:cc2e5d51a3132c19The line at the top of this page pins the label git:20261118.138ef0f, 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_5q4mu6kxxfa7c7a4)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in kdy1/kdy1-scripts/disk-cleanup since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of disk-cleanup from somewhere else? Ask it: where did my disk-cleanup come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 3 versions of this file, between Nov 11, 2026 and Nov 18, 2026, about one every 3 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261118.138ef0f latest | 2026-11-18 | 138ef0f | 5,863 B | A | view · diff |
| git:20261117.7255237 | 2026-11-17 | 7255237 | 5,847 B | A | view · diff |
| git:20261111.0a5687e | 2026-11-11 | 0a5687e | 6,316 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/disk-cleanup/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (5863 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
kdy1/kdy1-scripts · 34 stars · license none declared · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5q4mu6kxxfa7c7a4 GET https://markdownregistry.com/api/v1/resolve?ref=kdy1/kdy1-scripts/disk-cleanup GET https://markdownregistry.com/api/v1/blob/cc2e5d51a3132c194b11adbbc80a887cd88978a1086da7a9d81300fe7c0b20b3
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 kdy1/kdy1-scripts
Every file in kdy1/kdy1-scripts