hedgehog-orchestrating skillA
hedgehog-orchestrating is agent-read markdown (skill) from skyf0xx/hedgehog: Use at the start of any session on a project with a build graph (`.hedgehog/hedgehog.db`), and again at every claim/dispatch/verify cycle within it. Owns consuming the build graph — claiming task packets, delegating each to the layer's agent, running `hedgehog verify` to gate the commit, recording debt and decisions, the intent check at an intent's last layer, and when to clear context. Not for a build agent handed an already-claimed packet — that agent never claims, dispatches, or verifies; thi.
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
# Orchestrating the build `.hedgehog/hedgehog.db` is the source of truth for what's next — never re-derive build state from prose. To work from it: 1. Run `hedgehog claim --count N --owner <owner>`. It's atomic and lease-based, and returns up to N tasks (each with its own full STATUS/INTENT/RELEVANT RULES/INHERITED DEBT/INHERITED DECISIONS/WHY NOW/BLOCKED DOWNSTREAM/ALLOWED SCOPE/VERIFICATION packet) that the scheduler has already verified are safe to run together right now — scope and verify-radius disjoint. `--count` is a maximum, not a promise: a call may return fewer than N, or zero. `hedgehog ready` is a read-only preview of the claimable/held-back split (and why a task is held back — conflict with another claimable task, or exclusivity) before you claim. 2. Delegate each claimed packet to this core's loop skill (named in the project's core section), one dispatch per packet, running concurrently. 3. As each agent reports its packet done, run `hedgehog verify <task-id> --owner <owner>` **serially** — one at a time, even though the building happened concurrently, because verify writes git commits …
Read the whole file at its exact version.
How to install
mdr add skyf0xx/hedgehog/hedgehog-orchestrating@git:20260922.4bb2084mdr add skyf0xx/hedgehog/hedgehog-orchestrating@sha256:090ee4201b848711Pin 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_krnthfcqzqubf55w)
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 (9172 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
skyf0xx/hedgehog · 41 stars · license MIT · pushed 2026-09-23 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_krnthfcqzqubf55w GET https://markdownregistry.com/api/v1/resolve?ref=skyf0xx/hedgehog/hedgehog-orchestrating GET https://markdownregistry.com/api/v1/blob/090ee4201b848711b9ecd6485c913fb600a66337fdfa5b5b17060800eee55c0a
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.