headron-verification SKILL.md skillA

headron-verification from hlintel/headron is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add hlintel/headron/headron-verification@git:20261113.988de7a

Pins git:20261113.988de7a in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
hlintel/headron
Path
skills/headron-verification/SKILL.md
Versions recorded
1
Latest version
git:20261113.988de7a, committed Nov 13, 2026
Size
2,169 bytes
Repository stars
4
License
MIT

Verify a change with Headron before calling it done. Use when finishing a coding task in a repo with an atlas.yaml, or when asked to prove a change works.

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

# Headron verification

Headron is a verification layer for AI coding agents. The repository's atlas.yaml
declares which commands prove a change. Your job is not done when the code is
written; it is done when the checks the change owes have run and the receipt exists.

Full reference: https://headron.tech/llms-full.txt
Chat-only entry point: https://github.com/HLIntel/Headron/blob/main/CHAT.md

## Before you finish a change

1. Ask what the change owes: `headron route <file>` for each changed file, or
   `headron plan` for the declared change as a whole.
2. Read the lessons first: `headron failures --for <file-or-task>` returns recorded
   failure shapes for this kind of change, each with the move that replaces it.
3. Run the gates: `headron verify` runs every done gate once. `headron check`
   runs the whole contract; its exit code is the verdict.
4. Report verdicts exactly: PASS, FAIL, SKIP or NOT RUN. A check that did not run
   is never a pass. If a gate reports NOT RUN, say so, say why, and name the
   command that would close it. Never summarize a partial run as "all green".

## If the repository has no atlas.yaml
…

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_jttkhoqxqziktqqz/6531c7964da88e4913a59706c6b470113e90bbba3993edd04c8f87577334aa54.json

Then /plugin install headron-verification@markdownregistry-jttkhoqxqziktqqz in Claude Code. It installs git:20261113.988de7a, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add hlintel/headron/headron-verification@sha256:6531c7964da88e49

The line at the top of this page pins the label git:20261113.988de7a, 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_jttkhoqxqziktqqz.svg)](https://markdownregistry.com/a/art_jttkhoqxqziktqqz)

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 hlintel/headron/headron-verification 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 headron-verification from somewhere else? Ask it: where did my headron-verification 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 13, 2026.

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

versioncommittedcommitsizeaudit
git:20261113.988de7a latest2026-11-13 988de7a 2,169 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 (2169 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

hlintel/headron · 4 stars · license MIT · pushed 2026-11-18 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_jttkhoqxqziktqqz
GET https://markdownregistry.com/api/v1/resolve?ref=hlintel/headron/headron-verification
GET https://markdownregistry.com/api/v1/blob/6531c7964da88e4913a59706c6b470113e90bbba3993edd04c8f87577334aa54

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 hlintel/headron

headron SKILL.md skill
hlintel/headron · .agents/skills/headron/SKILL.md · Route, gate, verify and search the Headron engineering atlas. Use before editing any file in a Headron checkout, to…
git:20261117.6f99b9f · audit A · 4 stars
AGENTS.md AGENTS.md file
hlintel/headron · AGENTS.md
git:20261117.aee44af · audit A · 4 stars
CLAUDE.md CLAUDE.md file
hlintel/headron · CLAUDE.md
git:20261027.9024dde · audit A · 4 stars
llms.txt llms.txt file
hlintel/headron · llms.txt
git:20261117.aee44af · audit A · 4 stars
headron SKILL.md skill
hlintel/headron · models/chat/headron/SKILL.md · Engineering discipline for code, plans, reviews, debugging and done-claims: label evidence, name the proving gate…
git:20261117.aee44af · audit A · 4 stars
headron SKILL.md skill
hlintel/headron · skills/headron/SKILL.md · Record AI mistakes in the Headron ledger.
git:20261117.6f99b9f · audit A · 4 stars
land SKILL.md skill
hlintel/headron · skills/land/SKILL.md · Land this topic branch — rebase, run the suite, push, open the pull request and arm auto-merge, as one step.
git:20261117.6f99b9f · audit A · 4 stars
rekick SKILL.md skill
hlintel/headron · skills/rekick/SKILL.md · Restart the checks a forge outage stranded on an open pull request.
git:20261117.6f99b9f · audit A · 4 stars
sync SKILL.md skill
hlintel/headron · skills/sync/SKILL.md · Pull the default branch, arm stranded pull requests and remove finished topic-branch worktrees.
git:20261117.6f99b9f · audit A · 4 stars
run-workflow SKILL.md skill
hlintel/headron · skills/system/run-workflow/SKILL.md · How to write and run a dynamic workflow script with the `run_workflow` tool: a Python script that orchestrates many…
git:20261104.5d19a74 · audit A · 4 stars

Every file in hlintel/headron

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