grind-cron SKILL.md skillA
grind-cron from zackees/clud is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zackees/clud/grind-cron@git:20260926.0746f9aPins git:20260926.0746f9a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zackees/clud
- Path
crates/clud-bin/assets/skills/grind-cron/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260926.0746f9a, committed Sep 26, 2026
- First version recorded
- Sep 25, 2026
- Size
- 2,438 bytes
- Repository stars
- 14
- License
- a license file GitHub does not identify
/grind cron mode: hand repetition to the harness's native /loop, with each tick running the grind workflow sequentially on the next single issue.
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
<!-- managed-by: clud --> # /grind-cron The harness owns repetition. Do not build an external loop, iteration cap, or DONE/BLOCKED marker; see `docs/architecture/grind.md` in the clud repo. Issue one `/loop` whose body is: > Run `clud grind reconcile` first and report its stale lines. Then take the next open goal from <source> that has no open linked PR. If none > remain, end the loop. Otherwise start the Workflow named `grind-run` with > `mode: "sequential"`, that one goal, and these recorded answers: <models, > ci>. When it returns, do `/grind`'s Finish step: no files left behind, and > no rebase; confirm `git status` is clean. Ask the user nothing: every > answer was recorded up front. Restore `preflight` (Finish step 4: back > on the starting branch, `git pull --ff-only` only when that is `<main>`, > never a rebase) only when the loop ends. `<source>` is what `/grind-intake` resolved: the meta issue's children, the issue list, or the repo's issues page. Keep the run facts (the file `clud grind-facts path` prints) in place for the whole loop, with `mode` set to `sequential`: every tick runs in this session, so it reads the same file. …
Read the whole file at its exact version.
How to install
mdr add zackees/clud/grind-cron@sha256:0c112ef107d3fcefThe line at the top of this page pins the label git:20260926.0746f9a, 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_msriztsyqtoys4r6)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 25, 2026 and Sep 26, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260926.0746f9a latest | 2026-09-26 | 0746f9a | 2,438 B | A | view · diff |
| git:20260926.1b4dfa8 | 2026-09-26 | 1b4dfa8 | 2,145 B | A | view · diff |
| git:20260926.65cf607 | 2026-09-26 | 65cf607 | 1,960 B | A | view · diff |
| git:20260925.f50e143 | 2026-09-25 | f50e143 | 1,241 B | A | view · diff |
| git:20260925.ac82cd6 | 2026-09-25 | ac82cd6 | 1,188 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 (2438 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
zackees/clud · 14 stars · license a license file GitHub does not identify · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_msriztsyqtoys4r6 GET https://markdownregistry.com/api/v1/resolve?ref=zackees/clud/grind-cron GET https://markdownregistry.com/api/v1/blob/0c112ef107d3fcef7e47753dea26d2e6554ce4f16b54f2a37aba478b2ed3fc2b
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.