setup-agents-md skillA
setup-agents-md is agent-read markdown (skill) from openhands/extensions: Generate a high-quality, repo-specific AGENTS.md file that tells AI agents how to work effectively in a repository. Reads the actual repo to extract commands, structure, conventions, and guardrails — never generates generic boilerplate. Use when a user wants to create or improve their AGENTS.md, or after a readiness report identifies a missing agent instruction file..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Generate AGENTS.md Create a repo-specific AGENTS.md that gives AI agents the context they need to work effectively. Every section should reference real commands, real paths, and real conventions from the repository — not generic advice. ## Why this matters An AGENTS.md is the single highest-impact addition for agent readiness. It directly addresses features across multiple pillars: - **Agent Instructions**: agent instruction file, README with build/run/test, contributing guide, environment variable documentation - **Feedback Loops**: test run documentation — agents need exact commands - **Policy & Governance**: guardrails the agent must follow Without it, agents guess at build commands, miss project conventions, run the wrong test suite, and don't know what's dangerous. The best AGENTS.md files share the same core pattern: real commands, clear structure, explicit boundaries. ## How to run ### Step 0: Check for an existing AGENTS.md Look for an existing `AGENTS.md` (or `.agents/AGENTS.md`) in the repo root. If one exists, **do not rewrite it from scratch**. Instead, read the repo (Step 1), compare what you find against what's already documented, and suggest …
Read the whole file at its exact version.
How to install
mdr add openhands/extensions/setup-agents-md@git:20260408.eb2947bmdr add openhands/extensions/setup-agents-md@sha256:33abece9c9e27263Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_luv7pxyudbzakc6m)
1 badge views in 30 days
Versions
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 (6035 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
openhands/extensions · 150 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_luv7pxyudbzakc6m GET https://markdownregistry.com/api/v1/resolve?ref=openhands/extensions/setup-agents-md GET https://markdownregistry.com/api/v1/blob/33abece9c9e2726377e39d4adb0569ed46c6336e8bfc41e290462940e008a613
Your agent 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.