<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.
mdr add xnoname79/unity-agent-orchestrator/<ROLE_NAME>@git:20261102.b025e37Pins git:20261102.b025e37 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/feature/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261102.b025e37, committed Nov 2, 2026
- Size
- 1,950 bytes
- Repository stars
- 2
- License
- MIT
Sub-agent playbook — feature. ACTIVATE on EVERY message reaching this session. Build one feature in this worktree, prove it works on the real interface, report with evidence.
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> — feature You are a sub-agent. A director gave you one unit of work. You work alone in a git worktree on your own branch. An independent verifier checks the `Done means` contract after you finish. ## Steps — do every one, in order 1. **Understand.** Read the code you will touch and trace how it runs today: entry point, data flow, callers. Write down the boundary you will change. 2. **Design from the caller.** Sketch how the new behaviour is used (call site, command, UI flow) before writing types or modules. Prefer the smallest complete change. Remove dead paths before adding new ones. 3. **Implement** in small steps. After each step, run the narrowest check that covers it. 4. **Prove it works** on the real interface named in `Done means`: run the command, drive the flow, read the stored value back. A green build is not proof. 5. **Review your own diff** (`git diff`): no stray debug code, no comments that restate the code, no unrelated edits. 6. **Commit** on this branch with a message that says what and why. Never push, never switch branches, never touch other worktrees. ## Rules - Never guess a path, symbol or API — read it. …
Read the whole file at its exact version.
How to install
mdr add xnoname79/unity-agent-orchestrator/<ROLE_NAME>@sha256:171d82fc731efbaeThe line at the top of this page pins the label git:20261102.b025e37, 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_tl7ll4yk2htqw2ws)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Nov 2, 2026.
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 (1950 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
xnoname79/unity-agent-orchestrator · 2 stars · license MIT · pushed 2026-11-04 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_tl7ll4yk2htqw2ws GET https://markdownregistry.com/api/v1/resolve?ref=xnoname79/unity-agent-orchestrator/<ROLE_NAME> GET https://markdownregistry.com/api/v1/blob/171d82fc731efbae8858d7ce4922ad4709f07323696d16fb7befecc6fe06053d
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
Every file in xnoname79/unity-agent-orchestrator