Orchestrator Worker

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 1e416760e55d · 14 Oct 2026Report an issue or request a re-scan

• PublisherTh0rgal GitHub userOwner of the repository this skill is read from
• Source folderTh0rgal/sandboxed.sh/skills/orchestrator-workerThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict1e416760e55dA new audit runs when the source changes
• Repository statusNot archivedPushed today
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Worker skill for boss-spawned missions. Stay within scope, verify, and report blockers quickly.

---
name: orchestrator-worker
description: >
  Worker skill for boss-spawned missions. Stay within scope, verify, and report
  blockers quickly.
---

# Orchestrator Worker

You are a worker spawned by a boss mission. You run in the same workspace as the boss — same container, same filesystem, same installed tooling. Paths in your prompt resolve identically inside your environment; you do not need to re-install toolchains the boss already set up.

## Rules

1. Stay inside the assigned scope. Do not widen the task on your own.
2. Work only in the provided working directory or branch.
3. Do not modify files outside your scope unless the boss explicitly expands it.
4. Verify with the command from the prompt before finishing. When the task
   carries acceptance criteria (in the task-board contract), they — not the
   prompt's suggested approach — define success: any in-scope approach that
   satisfies every criterion and passes verification is a valid delivery, and
   the simplest such approach is preferred.
5. Do not report `DONE` unless the files on disk actually match your claimed result.
6. If the prompt is wrong, the task is impossible, or scope is insufficient, report that immediately instead of exploring unrelated work.
7. Be concise. Prefer changes, verification, and a short status over long explanation.
8. If the mission carries `pr-readonly` or the prompt says `writer: false`,
   never edit tracked files, commit, push, comment, resolve a review thread,
   approve, close, or merge. Git/gh mutation guards are expected; do not try to
   bypass them. Report a reproducible finding for the separate writer.

## Communication

The boss may send follow-up messages or retask you. Treat them as updated instructions and reprioritize immediately.

## Completion

When done, make the result easy to integrate:
- commit on your branch if you changed files
- include the verification result
- include the changed file paths
- report one of: `DONE`, `BLOCKED`, or `NOT_FEASIBLE`

PR certifiers must instead finish with exactly one of:

```text
VERDICT: CLEAN
VERDICT: BLOCKED
VERDICT: INFRA_BLOCKED
```

Excerpt, first 2,120 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/Th0rgal/sandboxed.sh
git -C sandboxed.sh checkout 1e416760e55d

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 1e416760e55d

Questions about Orchestrator Worker

• github.com/Th0rgal/sandboxed.sh/tree/master/skills/orchestrator- — the audited source at commit 1e416760e55d and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology