autonomous-loops SKILL.md skillA
autonomous-loops from pekral/cursor-rules is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pekral/cursor-rules/autonomous-loops@git:20261003.14c8a0bPins git:20261003.14c8a0b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pekral/cursor-rules
- Path
skills/autonomous-loops/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261003.14c8a0b, committed Oct 3, 2026
- First version recorded
- Jun 15, 2026
- Size
- 9,243 bytes
- Repository stars
- 12
- License
- MIT
Use when choosing how to run Claude Code autonomously on this project — from a single sequential pipeline to multi-agent DAG orchestration. A reference catalog of loop patterns anchored to this repo's real tooling (resolve-issue, code-review-github, process-code-review, merge-github-pr, /loop), with composer build / composer skill-check as the quality gate between iterations.
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
This is a reference skill. It does not run a loop itself — it helps you pick the right autonomous-loop architecture for a task and wire it to this project's existing skills, gates, and CLI tooling. Patterns are ordered simplest → most complex. Use the lightest one that fits. ## Constraints - Apply `@rules/git/general.mdc` — never push to `main`, one logical change per commit, English commit messages, worktree/branch per work unit. - Apply `@rules/code-review/general.mdc` to every review stage in a loop — reviewers are read-only and must not be the same context that wrote the code. - `composer build` and `composer skill-check` are non-negotiable gates between iterations. An iteration that does not pass them is not "done" and must not advance the loop or merge. - Every loop needs an explicit stop condition (max iterations, no open work, or a documented blocker). Never run unbounded. - Stop on blockers, never force through them: merge conflict, failing CI, unresolved Critical/Moderate findings, or a gate failure ends the loop with a report. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_vzc63tilejasjkiv/27830b5d2f71f1f53c462a56e1b6da099f064d48798d3ecf9d27a0c9d1cc54d5.json
Then /plugin install autonomous-loops@markdownregistry-vzc63tilejasjkiv in Claude Code. It installs git:20261003.14c8a0b, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add pekral/cursor-rules/autonomous-loops@sha256:27830b5d2f71f1f5The line at the top of this page pins the label git:20261003.14c8a0b, 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_vzc63tilejasjkiv)
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 pekral/cursor-rules/autonomous-loops 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 autonomous-loops from somewhere else? Ask it: where did my autonomous-loops 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 Jun 15, 2026 and Oct 3, 2026, about one every 55 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261003.14c8a0b latest | 2026-10-03 | 14c8a0b | 9,243 B | A | view · diff |
| git:20260618.6465dda | 2026-06-18 | 6465dda | 9,260 B | A | view · diff |
| git:20260615.0d1a309 | 2026-06-15 | 0d1a309 | 8,992 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/autonomous-loops/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 (9243 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
pekral/cursor-rules · 12 stars · license MIT · pushed 2026-10-03 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_vzc63tilejasjkiv GET https://markdownregistry.com/api/v1/resolve?ref=pekral/cursor-rules/autonomous-loops GET https://markdownregistry.com/api/v1/blob/27830b5d2f71f1f53c462a56e1b6da099f064d48798d3ecf9d27a0c9d1cc54d5
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 pekral/cursor-rules
Every file in pekral/cursor-rules