feature-map SKILL.md skillA
feature-map from dababonpro/human-approved-agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dababonpro/human-approved-agents/feature-map@git:20261108.4b37627Pins git:20261108.4b37627 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/feature-map/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261108.4b37627, committed Nov 8, 2026
- First version recorded
- Nov 2, 2026
- Size
- 7,653 bytes
- Repository stars
- 5
- License
- MIT
Procedure for keeping a repo's important features from regressing, by recording what must stay true for each feature, which code it lives in, and what proves it, then checking every change against that map. Use it when setting up regression protection, when a task or PR might break existing behaviour, when an agent will change code in a repo with a features.toml, when asked for a feature map, behaviour inventory or regression guard, or when a bug has come back. Also use it before calling a…
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
# Feature map Tests that pass show the checked behaviour still works. They do not show which behaviour matters, or whether this change touched it. A feature map records both in a file the repo owns. It also flags a deleted, skipped or edited test for a person. It does not judge a test edit, and its skip patterns are a tripwire, not a defence. Each entry says what must stay true, where the code lives, and what proves it. A script then matches a change to its features, runs their proof, and fails on gaps. No feature map replaces reading the code. It catches broken promises, not poor design. ## 1. Check it fits Use it on a repo that changes often and has behaviour someone would be hurt to lose. Skip it for throwaway code. Do not map everything. A full map goes stale, and a stale map is ignored. ## 2. Create the map 1. List the 5 to 10 flows that would hurt most if they broke. Ask the owner. Look at incidents, repeat bugs and the fixes in git history, because a bug that came back once tends to come back again. 2. Copy `references/features.template.toml` to `features.toml` at the repo root. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_7wtxwdhquhsjm35f/1f92810da082bd15f18710d22b10153fe256e1d6d04bfbe57ec69d69159faa7e.json
Then /plugin install feature-map@markdownregistry-7wtxwdhquhsjm35f in Claude Code. It installs git:20261108.4b37627, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add dababonpro/human-approved-agents/feature-map@sha256:1f92810da082bd15The line at the top of this page pins the label git:20261108.4b37627, 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_7wtxwdhquhsjm35f)
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 dababonpro/human-approved-agents/feature-map 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 feature-map from somewhere else? Ask it: where did my feature-map 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 2 versions of this file, between Nov 2, 2026 and Nov 8, 2026, about one every 6 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261108.4b37627 latest | 2026-11-08 | 4b37627 | 7,653 B | A | view · diff |
| git:20261102.7e43d29 | 2026-11-02 | 7e43d29 | 7,444 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/feature-map/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 (7653 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
dababonpro/human-approved-agents · 5 stars · license MIT · pushed 2026-11-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7wtxwdhquhsjm35f GET https://markdownregistry.com/api/v1/resolve?ref=dababonpro/human-approved-agents/feature-map GET https://markdownregistry.com/api/v1/blob/1f92810da082bd15f18710d22b10153fe256e1d6d04bfbe57ec69d69159faa7e
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
Every file in dababonpro/human-approved-agents