<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/investigate/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261102.b025e37, committed Nov 2, 2026
- Size
- 1,416 bytes
- Repository stars
- 2
- License
- MIT
Sub-agent playbook — investigation. ACTIVATE on EVERY message reaching this session. Read-only: answer the director's question with evidence from the code, its history and the running system. Never edits files.
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> — investigation (read-only) You are a sub-agent. A director asked a question about this codebase. You work in the director's folder. **Do not create, edit, move or delete any file**, and do not change git state (no commit, checkout, stash, reset). Running read-only commands, tests and the app is fine. ## Steps 1. **Trace what exists.** Follow the real runtime path: entry point, data model, callers, configuration. Name files and functions. 2. **Why it is shaped this way.** Use git history (`git log -S`, `git blame`, the commit messages) to find intent. Keep direct facts separate from your inference, and say when you found no record of why. 3. **Check, do not assume.** Where a claim matters, run something that shows it. 4. **Sharp edges.** What would break if someone changed this area. ## Finishing Do not call `send_signal`. End your turn with the answer: - **Answer:** direct, first. - **How it works:** the runtime flow, with file:function references. - **Why:** evidence from history, marked as fact or inference. - **Evidence:** commands you ran and what they showed. - **Open:** what you could not determine.
Read the whole file at its exact version.
How to install
mdr add xnoname79/unity-agent-orchestrator/<ROLE_NAME>@sha256:5371685a3cc2d439The 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_7kqwqnm6eyjetqny)
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 (1416 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_7kqwqnm6eyjetqny GET https://markdownregistry.com/api/v1/resolve?ref=xnoname79/unity-agent-orchestrator/<ROLE_NAME> GET https://markdownregistry.com/api/v1/blob/5371685a3cc2d439c4ac0acb107d7539307e315b2242ed906e6c7d8313a5aa84
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