auditAnswers questions about how the Harness is actually used and where it falls short, from local transcripts, the delegation ledger, shim firings, and the component catalog across every synced machine. Use when asked which skills or rules are used or unused, which shims still fire or could retire, what
delegateDelegates bounded execution, fixed-target or independent review, or computer-use checks to a subagent or Codex through Harness routing. Use when an agent hands such work to a worker.
fleetRuns commands on the developer's other machines over SSH and enrolls or removes machines from the Harness fleet; inventory and public keys live in the private agents repo, never private keys. Run /harness:fleet to have the agent run a command, read a log, check a build, or restart a service on anoth
model-rubricCreates or refreshes this developer's user-global model-routing rubric, which decides which model does which work, at ${XDG_CONFIG_HOME:-$HOME/.config}/studio-moser/model-rubric.yml (synced through the agents repo when present). Use when asked to set up or refresh the model rubric, when it is stale,
risk-gateDecides whether repository work needs a written plan, recovery point, or independent review under Harness risk rules. Use before work touching security, money, persisted data, a public contract, several repositories, no testing seam, or more than one context window, or when the user explicitly reque
setupSets up or checks Harness for this developer: agents repo, links, runtimes, and the model rubric. Use when Harness needs first-time setup or a health check.
syncReconciles and publishes this machine's portable agent configuration with the guarded Harness sync script. Use when asked to sync agent config.