autonomous-run SKILL.md skillA
autonomous-run from dayfinggg/openai-codex-agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dayfinggg/openai-codex-agent-skills/autonomous-run@git:20261117.080857bPins git:20261117.080857b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dayfinggg/openai-codex-agent-skills
- Path
codex/skills/autonomous-run/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261117.080857b, committed Nov 17, 2026
- Size
- 1,322 bytes
- Repository stars
- 8
- License
- MIT
Carry an explicitly unattended, headless, or multi-session task through its stated finish condition. Use when the user says to continue without check-ins, work until a result, or resume long-running work after compaction. Do not infer a persistent Codex Goal from an ordinary task.
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
# Unattended runs Use this skill when the user expects work to proceed without routine check-ins, through a headless run, or across compaction. Ordinary interactive tasks do not need a progress log solely because they take several steps. Define the finish condition from the user's request and the check that would prove it. Read applicable project instructions and existing run records before continuing earlier work. Make reversible choices within scope and keep moving on work that does not depend on user input. Do not broaden authorization, contact people, or make hard-to-reverse external changes beyond what the request permits. For a run likely to span sessions or compaction, read [Long-run record and stopping conditions](references/long-runs.md) before setting up its records. Use the runtime's Goal tools only when the user explicitly requests a persisted goal or the environment has already established one. Never create a Goal merely because this workflow is active.
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_hwowr5zpof6tymn6/bd746c2ad65d7f6443fb3d07dd635925fc25827a6f58fed47aad946d3ce6485a.json
Then /plugin install autonomous-run@markdownregistry-hwowr5zpof6tymn6 in Claude Code. It installs git:20261117.080857b, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add dayfinggg/openai-codex-agent-skills/autonomous-run@sha256:bd746c2ad65d7f64The line at the top of this page pins the label git:20261117.080857b, 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_hwowr5zpof6tymn6)
1 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 dayfinggg/openai-codex-agent-skills/autonomous-run 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-run from somewhere else? Ask it: where did my autonomous-run 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 1 version of this file, committed on Nov 17, 2026.
Watch this file (sign in, one email per new version)
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-run/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 (1322 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
dayfinggg/openai-codex-agent-skills · 8 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hwowr5zpof6tymn6 GET https://markdownregistry.com/api/v1/resolve?ref=dayfinggg/openai-codex-agent-skills/autonomous-run GET https://markdownregistry.com/api/v1/blob/bd746c2ad65d7f6443fb3d07dd635925fc25827a6f58fed47aad946d3ce6485a
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 dayfinggg/openai-codex-agent-skills
Every file in dayfinggg/openai-codex-agent-skills