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.
git clone --depth 1 https://github.com/larcane97/clausonaWrote 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.
[](https://agentmods.dev/plugins/larcane97/clausona/orca-fleet)<a href="https://agentmods.dev/plugins/larcane97/clausona/orca-fleet"><img src="https://agentmods.dev/badge/plugins/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.
<a href="https://agentmods.dev/plugins/larcane97/clausona/orca-fleet"><img src="https://agentmods.dev/badge/plugins/larcane97/clausona/orca-fleet.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
This is a copy
92% identical to herdr-fleet — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"name": "orca-fleet",
"version": "0.1.2",
"description": "Run parallel agents in Orca worktrees, each on its own clausona account or API model (Claude Code or Codex), then check and retire them.",
"author": { "name": "larcane97", "url": "https://github.com/larcane97" },
"homepage": "https://github.com/larcane97/clausona/blob/main/docs/usecases/orca-fleet.md",
"repository": "https://github.com/larcane97/clausona",
"license": "MIT",
"keywords": ["orca", "clausona", "multi-account", "parallel-agents", "orchestration", "codex"],
"dependencies": ["fleet-core"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 105 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 58b22f3e6c69
- 16d ago First seen · 12 lines scan A d9938c66de1c
orca-fleet is a plugin published in the GitHub repository larcane97/clausona (57 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. It is 92% identical to herdr-fleet, differing in 8 lines, and is treated as a copy.
Other plugins, from other repositories
wend
Find, recover, and resume your past Claude Code sessions from local history — keyword search, pre-compaction recovery, and worktree topology.
pr-provenance-stamp
Embeds a reviewer-facing provenance receipt into your PR body when Claude runs gh pr create (or glab mr create). A PostToolUse hook (async, zero added latency) records a per-session ledger: tool calls, agent-authored lines, and every test/typecheck command with its real exit code; a PreToolUse (Bash) hook then rewr.
aigon
aigon. Aigon is a local, open-source, spec-first software-delivery orchestrator for coding agents. It takes a Git-backed feature spec through isolated implementation, cross-agent review, and merge—using the agents and subscriptions you already have.
cc-safe-setup
909 safety hooks for Claude Code — prevent file deletion, credential leaks, git disasters, and token waste during autonomous AI coding sessions.
anotifier
Desktop & phone notifications for AI coding agents in VS Code and CLI. Supports Claude Code, Codex, Gemini CLI, Antigravity CLI, and Cursor.
agentclaim
File ownership for parallel AI agents in one git working tree. Stops them silently overwriting each other.