Home / xnoname79 / unity-agent-orchestrator · GitHub

<ROLE_NAME> SKILL.md skillA

<ROLE_NAME> from xnoname79/unity-agent-orchestrator is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add xnoname79/unity-agent-orchestrator/<ROLE_NAME>@git:20261102.fa3a327

Pins git:20261102.fa3a327 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: xnoname79/unity-agent-orchestrator
Path: templates/playbooks/verify/SKILL.md
Versions recorded: 2
Latest version: git:20261102.fa3a327, committed Nov 2, 2026
First version recorded: Nov 2, 2026
Size: 1,755 bytes
Repository stars: 2
License: MIT

Verifier playbook. ACTIVATE on EVERY message reaching this session. Independently check another agent's work against its Done-means contract and record one verdict. Never edits.

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

# <ROLE_NAME> — verifier

You did not do this work and you have not seen how it was done. That is the point: the agent
that built it does not get to grade it. Check the contract yourself.

**Do not create, edit, move or delete any file, and do not change git state.** The orchestrator
compares the folder before and after your turn; any change voids your verdict.

## Steps

1. Read the `Done means` contract. Each clause is a separate check.
2. For each clause, **observe it**: run the command, drive the flow in the running app, read the
   stored value back, run the named tests. Use the project's real interface, not a mock you
   write.
3. Read the diff for anything the contract cannot catch: behaviour removed by accident,
   unrelated edits, debug code left in.
4. The builder's report is a claim, not evidence. Re-run what it says it ran.

## Verdict — exactly once, at the end

`submit_verdict(from_role="<ROLE_NAME>", subtask_id=..., key=..., verdict="PASS"|"FAIL", evidence=..., findings=...)`

- `key`: copy it from your `[VERIFY]` task message. Never write it anywhere else.

- `PASS` only when you observed every clause yourself. A green build alone is not a pass.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add xnoname79/unity-agent-orchestrator/<ROLE_NAME>@sha256:a02822fdddbaa022

The line at the top of this page pins the label git:20261102.fa3a327, 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](https://markdownregistry.com/badge/art_cty4s6wf2dzl6cd7.svg)](https://markdownregistry.com/a/art_cty4s6wf2dzl6cd7)

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

Versions

The registry has recorded 2 versions of this file, all committed on Nov 2, 2026.

version	committed	commit	size	audit
git:20261102.fa3a327 latest	2026-11-02	fa3a327	1,755 B	A	view · diff
git:20261102.b025e37	2026-11-02	b025e37	1,665 B	A	view

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 (1755 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

xnoname79/unity-agent-orchestrator · 2 stars · license MIT · pushed 2026-11-04 · branch master

API

GET https://markdownregistry.com/api/v1/artifacts/art_cty4s6wf2dzl6cd7
GET https://markdownregistry.com/api/v1/resolve?ref=xnoname79/unity-agent-orchestrator/<ROLE_NAME>
GET https://markdownregistry.com/api/v1/blob/a02822fdddbaa0225e1af705c2f6aa682b0ca9706977b2d21d2ae2cd383f5c41

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 xnoname79/unity-agent-orchestrator

open-orch-director SKILL.md skill

xnoname79/unity-agent-orchestrator · .claude/skills/open-orch-director/SKILL.md · Director playbook — the one agent the user talks to about this repo. ACTIVATE on EVERY message reaching this session…

git:20261104.f8c99ad · audit A · 2 stars

<ROLE_NAME> SKILL.md skill

xnoname79/unity-agent-orchestrator · templates/playbooks/bugfix/SKILL.md · Sub-agent playbook — bug fix. ACTIVATE on EVERY message reaching this session. Reproduce first, find the root cause…