A skill for running several coding agents side by side in Orca worktrees, with each worker assigned a clausona profile. Profiles can represent different Claude Code or Codex accounts or API models.

Use it when working in Orca and you want parallel agents to handle separate coding tasks or approaches.

It provides the operating steps for distributing work across agents without mixing their working files. It also covers checking the workers and shutting them down when their tasks are done.

orca-fleet — Skill for Claude Code by larcane97/clausona

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add larcane97/clausona --skill orca-fleet

Clone the repo

git clone --depth 1 https://github.com/larcane97/clausona

Made for: Claude Code.

Or install orca-fleet, the plugin that ships this one along with the rest of its 1 skill.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/larcane97/clausona/orca-fleet/github.svg)](https://agentmods.dev/skills/larcane97/clausona/orca-fleet)

Your own site

<a href="https://agentmods.dev/skills/larcane97/clausona/orca-fleet"><img src="https://agentmods.dev/badge/skills/larcane97/clausona/orca-fleet/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/larcane97/clausona/orca-fleet"><img src="https://agentmods.dev/badge/skills/larcane97/clausona/orca-fleet.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 105 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,093 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00105	$0.02093
Opus 5.5	$0.00042	$0.00837
Sonnet 5.5	$0.00021	$0.00419
Haiku 4.5	$0.00011	$0.00209

Measured 9d ago against content hash ac1db7ea055e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

orca-fleet scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/orca-fleet/skills/orca-fleet/SKILL.md · 129 lines

How it starts

The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Orca fleet on clausona profiles

Orca runs agents side by side in git worktrees and lists them in its sidebar. clausona puts each terminal's agent on the profile you choose.

0. Load the shared rules

Load the fleet-core skill first and follow it; this skill only adds the Orca steps. In Claude Code, invoke it with the Skill tool. If that fails, or you run in Codex, read the first of these files that exists, where <base> is this skill's base directory:

<base>/../../../fleet-core/skills/fleet-core/SKILL.md
<base>/../../../../fleet-core/*/skills/fleet-core/SKILL.md (if several versions match, read the highest)

If none exists, stop and tell the user to install it: claude plugin install fleet-core@clausona in Claude Code, or codex plugin add fleet-core@clausona in Codex.

1. Before anything

Stop and tell the user what is missing if any of these fails.

orca status shows runtimeReachable: true. If Orca is not open, ask the user to open it.
orca repo list --json lists the repo. If not, ask before adding it with orca repo add --path <repo> --json: it adds the repo to the user's Orca sidebar.
The repo has a remote: workers push their branches.

Pass --json and read handles and paths from the reply; never guess them. Orca runs on macOS, Linux and Windows, and the commands below are the same on each.

Orca has its own account switcher and orchestration commands. Do not use them for workers: clausona run decides each worker's account. Orca also sets CODEX_HOME in its terminals, so a bare codex there runs on Orca's account; clausona run overrides it.

2. Starting a worker

For each task, after fleet-core picked its profile:

Worktree. orca worktree create --repo path:<repo> --name fleet-<task> --json, and record .result.worktree.path (under ~/orca/workspaces/ by default). Then orca worktree set --worktree path:<worktree> --display-name "<task> · <profile>", so the sidebar shows which account runs where. Keep it under 26 characters.
Terminal. orca terminal create --worktree path:<worktree> --json, and record .result.terminal.handle. Do not pass --command: the shell's start-up output can swallow it. Do not rely on --title either: the shell renames the tab.
Wait for the shell. Read orca terminal show --terminal <handle> --json once a second until its lastOutputAt is at least two seconds old, for at most 20 seconds. orca terminal wait does not work for a plain shell.
Start. orca terminal send --terminal <handle> --text "clausona run <profile> -- <args>" --enter, with the arguments from fleet-core section 4. Codex workers keep --disable hooks.
Check it started. After about 10 seconds, run orca terminal show --terminal <handle> --json. The tool has started when .result.terminal.title is no longer the shell's (Claude Code sets ✳ Claude Code), or when orca worktree ps --json lists an agent under the worktree. The preview field shows the screen, but it can lag behind a full-screen app that is still starting, so never resend the launch line on the preview alone: a line sent to a running Claude Code becomes its first prompt. Send it once more only when the title is still the shell's after 20 seconds and the preview shows the launch line never ran. Otherwise tell the user what the screen shows.
Folder trust. The first worker of a profile in a repo that profile never trusted asks whether to trust the folder. Answer only that question, and only about this repository:
- Claude Code ("Is this a project you created or one you trust?"): the highlighted answer is "No, exit". Send the down arrow, orca terminal send --terminal <handle> --text $'\e[B' (PowerShell: --text "$([char]27)[B"), then orca terminal send --terminal <handle> --enter.
- Codex ("Trust this folder?"): the highlighted answer is "1. Trust and continue". Send orca terminal send --terminal <handle> --enter.
Brief. Write it as fleet-core section 5 says, then orca terminal send --terminal <handle> --text "Read .fleet-brief.md in this folder and do what it says." --enter, and start waiting on it (section 3). In Codex, wait only once every worker has its brief.
Record the handle, worktree, branch and profile in the table.

Read the full file on GitHub · 129 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago Changed · +6 lines ac1db7ea055e
16d ago First seen · 123 lines · 105 tokens per session scan A 8a30e1efd34e

Subscribe to this mod's changes

orca-fleet is a skill published in the GitHub repository larcane97/clausona (57 stars, last pushed 5d ago), licensed MIT. It adds 105 tokens to every session and 2,093 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-10.

Building agents Claude Code Git and workflow account-manager account-switcher ai-coding claude cli

autofix-pr

Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…

QwenLM/qwen-code · 123 tokens

repo-hygiene

Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.

QwenLM/qwen-code · 48 tokens

create-issue

Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.

QwenLM/qwen-code · 26 tokens

docs-update-from-diff

Review local code changes with git diff and update the official docs under docs/ to match. Use when the user asks to document current uncommitted work, sync docs with local changes, update docs after a feature or refactor, or when phrases like "git diff", "local changes", "update docs", or "official docs" appear.

QwenLM/qwen-code · 75 tokens

prepare-pr

Prepare GitHub pull request title and body files from the current branch diff, especially for non-interactive CI/autofix flows that must follow the repository PR template without pushing or creating the PR.

QwenLM/qwen-code · 42 tokens

triage

Gatekeep and review GitHub issues and pull requests for Qwen Code maintainers. Use for GitHub Action issue triage, PR admission checks, product-direction review, KISS-focused PR review, and staged bilingual GitHub comments.

QwenLM/qwen-code · 50 tokens