setup-agent-rules SKILL.md skillA

setup-agent-rules from dababonpro/human-approved-agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add dababonpro/human-approved-agents/setup-agent-rules@git:20261108.9b5e01b

Pins git:20261108.9b5e01b in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
dababonpro/human-approved-agents
Path
skills/setup-agent-rules/SKILL.md
Versions recorded
1
Latest version
git:20261108.9b5e01b, committed Nov 8, 2026
Size
4,383 bytes
Repository stars
5
License
MIT

Set up the Human-Approved Agent Playbook's agent rules (AGENTS.md) in the current project for the person, by reading the project, asking them a few short questions, filling the template from their answers, and writing the file only after they approve it. Use it when someone asks to set up, install, add or adopt the agent rules, an AGENTS.md, or the human-approved agent playbook in a project.

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

# Set up the agent rules

The person should not have to edit the template by hand. Read what the project already shows, ask only what it cannot tell you, and write the file after they approve it.

## Steps

1. **Get the template.** Use `templates/AGENTS.md` two folders above this skill's folder, which is there when the skill comes with the playbook. If it is missing, fetch `https://raw.githubusercontent.com/dababonpro/human-approved-agents/main/templates/AGENTS.md`. If you can do neither, stop and say so. Never write the rules from memory.
2. **Check the project root.** If an `AGENTS.md` already exists, do not replace it. Say so, and ask whether to stop, write the new rules to `AGENTS.playbook.md` for the person to merge, or replace the old file. Note whether a `CLAUDE.md` or `CLAUDE.local.md` exists.
3. **Read the project to suggest answers.** Read only. Useful places: the README, `package.json` scripts, `Makefile`, `pyproject.toml`, CI workflows, deploy settings and config file names. For a config or `.env` file, read the setting names only and hide the values. Never print a secret value.
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_zpmaiah7liwnerkm/134d4fb611c9f1ae60a36faa455534c94156e8aed73b5fd66ffd47475d83641e.json

Then /plugin install setup-agent-rules@markdownregistry-zpmaiah7liwnerkm in Claude Code. It installs git:20261108.9b5e01b, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add dababonpro/human-approved-agents/setup-agent-rules@sha256:134d4fb611c9f1ae

The line at the top of this page pins the label git:20261108.9b5e01b, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_zpmaiah7liwnerkm.svg)](https://markdownregistry.com/a/art_zpmaiah7liwnerkm)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in dababonpro/human-approved-agents/setup-agent-rules 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 setup-agent-rules from somewhere else? Ask it: where did my setup-agent-rules 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 8, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261108.9b5e01b latest2026-11-08 9b5e01b 4,383 BA view
Keep it current by itself, install once

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.

Install on GitHub

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.

Keep it current by itself

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.

Check a whole project

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

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (4383 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

GitHub

dababonpro/human-approved-agents · 5 stars · license MIT · pushed 2026-11-13 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_zpmaiah7liwnerkm
GET https://markdownregistry.com/api/v1/resolve?ref=dababonpro/human-approved-agents/setup-agent-rules
GET https://markdownregistry.com/api/v1/blob/134d4fb611c9f1ae60a36faa455534c94156e8aed73b5fd66ffd47475d83641e

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 dababonpro/human-approved-agents

AGENTS.md AGENTS.md file
dababonpro/human-approved-agents · AGENTS.md
git:20261102.7e43d29 · audit A · 5 stars
feature-map SKILL.md skill
dababonpro/human-approved-agents · skills/feature-map/SKILL.md · Procedure for keeping a repo's important features from regressing, by recording what must stay true for each feature…
git:20261108.4b37627 · audit A · 5 stars
preview-then-execute SKILL.md skill
dababonpro/human-approved-agents · skills/preview-then-execute/SKILL.md · Procedure for any action that changes data, merges code, sends something outside the company, deploys, changes…
git:20261108.4b37627 · audit A · 5 stars
session-handover SKILL.md skill
dababonpro/human-approved-agents · skills/session-handover/SKILL.md · Procedure for ending a working session so the next person or agent can continue without guessing, and for picking up…
git:20261108.4b37627 · audit A · 5 stars
setup-playbook SKILL.md skill
dababonpro/human-approved-agents · skills/setup-playbook/SKILL.md · Set up the whole Human-Approved Agent Playbook in the current project for the person, from one short interview. Draft…
git:20261110.85cae1c · audit A · 5 stars
verify-the-result SKILL.md skill
dababonpro/human-approved-agents · skills/verify-the-result/SKILL.md · Procedure for confirming that work actually succeeded before calling it done. Use it after any write, data move…
git:20261108.4b37627 · audit A · 5 stars
AGENTS.md@templates AGENTS.md file
dababonpro/human-approved-agents · templates/AGENTS.md
git:20261108.4b37627 · audit A · 5 stars

Every file in dababonpro/human-approved-agents

Browse by kind, by grade A, or by owner.