headron SKILL.md skillA

headron 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@git:20261117.aee44af

Pins git:20261117.aee44af in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
hlintel/headron
Path
models/chat/headron/SKILL.md
Versions recorded
5
Latest version
git:20261117.aee44af, committed Nov 17, 2026
First version recorded
Nov 13, 2026
Size
9,382 bytes
Repository stars
4
License
MIT

Engineering discipline for code, plans, reviews, debugging and done-claims: label evidence, name the proving gate, catch known failure shapes.

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 in a chat (contract v3.64.0)

GENERATED from atlas.yaml by `python scripts/atlas.py index --write`. Do not edit.

Apply to every answer that writes, reviews, plans or debugs code, or claims something works. Make every claim checkable. If you can run the gate (a sandbox, code execution), run it and label the result CONFIRMED; if you cannot, name the command that would check it.

Scale the ceremony to the change: a snippet of a few lines, a one-line fix or a question with no change gets one line naming its gate, never the full card.

## Rules for every answer

Where a rule says CHAT.md or tools.yaml, read `references/routes.md`: it carries both.

You are working with Headron Software (github.com/HLIntel/Headron).
1. Start with the user's task and constraints. Use only the context needed; route a file to its pack when a change needs verification.
2. Check the available pack before naming its commands or versions. If unavailable, say what is missing; never guess.
3. Distinguish observed evidence, inference and uncertainty. Never present a proposed check as a passing result.
…

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_4r3t5xgluuyopnzt/cfe621302ebc1bd0c6018bb1a4b282e9550af107aa64f1dabcbfdd250d32e70d.json

Then /plugin install headron@markdownregistry-4r3t5xgluuyopnzt in Claude Code. It installs git:20261117.aee44af, 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@sha256:cfe621302ebc1bd0

The line at the top of this page pins the label git:20261117.aee44af, 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_4r3t5xgluuyopnzt.svg)](https://markdownregistry.com/a/art_4r3t5xgluuyopnzt)

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 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 from somewhere else? Ask it: where did my headron 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 5 versions of this file, between Nov 13, 2026 and Nov 17, 2026, about one every day.

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

versioncommittedcommitsizeaudit
git:20261117.aee44af latest2026-11-17 aee44af 9,382 BA view · diff
git:20261117.c3795df2026-11-17 c3795df 9,382 BA view · diff
git:20261117.644c4812026-11-17 644c481 9,382 BA view · diff
git:20261117.cbfadd02026-11-17 cbfadd0 9,419 BA view · diff
git:20261113.206e6c22026-11-13 206e6c2 9,419 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 (9382 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_4r3t5xgluuyopnzt
GET https://markdownregistry.com/api/v1/resolve?ref=hlintel/headron/headron
GET https://markdownregistry.com/api/v1/blob/cfe621302ebc1bd0c6018bb1a4b282e9550af107aa64f1dabcbfdd250d32e70d

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-verification SKILL.md skill
hlintel/headron · skills/headron-verification/SKILL.md · Verify a change with Headron before calling it done. Use when finishing a coding task in a repo with an atlas.yaml, or…
git:20261113.988de7a · 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

Other files named 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
headron SKILL.md skill
hlintel/headron · skills/headron/SKILL.md · Record AI mistakes in the Headron ledger.
git:20261117.6f99b9f · audit A · 4 stars

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