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.
npx skills add larcane97/clausona --skill tmux-fleetgit 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/skills/larcane97/clausona/tmux-fleet)<a href="https://agentmods.dev/skills/larcane97/clausona/tmux-fleet"><img src="https://agentmods.dev/badge/skills/larcane97/clausona/tmux-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/skills/larcane97/clausona/tmux-fleet"><img src="https://agentmods.dev/badge/skills/larcane97/clausona/tmux-fleet.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00115 | $0.02716 |
| Opus 5.5 | $0.00046 | $0.01086 |
| Sonnet 5.5 | $0.00023 | $0.00543 |
| Haiku 4.5 | $0.00012 | $0.00272 |
Grade A, and why
tmux-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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tmux fleet on clausona profiles
tmux runs each worker in a window of the session you are in, and its status bar lists them. clausona puts each window's agent on the profile you choose. tmux cannot tell what an agent is doing, so the helper that ships with this skill gives each worker a way to report it, and waits on those reports.
0. Load the shared rules
Load the fleet-core skill first and follow it; this skill only adds the tmux 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
Below, H means node <base>/scripts/tmux-fleet.mjs. Write it out in full, or start the command
with the function H() { node <base>/scripts/tmux-fleet.mjs "$@"; }. Never put it in a variable:
zsh does not split a variable into words. Every H command prints JSON, except H read, which
prints the screen. Read window and pane ids from the JSON; never guess them.
Stop and tell the user what is missing if any of these fails.
H statusprints"ok": true. It fails outside tmux: the helper drives the tmux session you run in, so do not drive tmux from outside it. In Codex,TMUXalso looks unset when Codex hides the environment (fleet-core, Shells). If it does, do not tell the user they are outside tmux: tell them to start Codex again in this pane with-c shell_environment_policy.inherit=all. tmux runs on macOS, Linux and WSL. On Windows without WSL there is no tmux: suggest herdr-fleet or orca-fleet.- Pass on any
warningsit prints. Withbell-actionset tononeorcurrentin the user's tmux (orother, while the user looks at that window), a Codex worker is noticed only by the quiet check (section 3). - The repo has a remote: workers push their branches.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 157 lines · 115 tokens per session scan A 1d15ca0aff45
tmux-fleet is a skill published in the GitHub repository larcane97/clausona (57 stars, last pushed 5d ago), licensed MIT. It adds 115 tokens to every session and 2,716 once invoked, about $0.0005 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-17.
Other skills, from other repositories
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern. For many independent single-turn transforms (translate/rewrite/extract each file into a new file) that can wait…
batch-api
Prepare a many-file, single-turn transform (translate, rewrite, extract) as a plan and submit it to the asynchronous, half-price DashScope Batch API; results are delivered as new files hours later. Invoke explicitly with /batch-api.
loop
Create a loop that runs a prompt now and follows up either on a fixed schedule or through self-paced wakeups. Usage - /loop check the build, /loop 5m check the build, /loop check the PR every 30m. /loop list to show jobs, /loop clear to cancel all.
openrig-herdr
Use when opening OpenRig fleet terminals as a herdr wall — turning a rig, pod, mission, slice, or saved view into live interactive agent tiles via rig terminal, watching another rig read-only, or driving herdr on an agent's request ("open all my rigs + a mission as views"). Covers the rig terminal open|views|status…
mission-slice-sop
Use when starting, building, handing off, restoring, or closing a mission or slice under the default lightweight SDLC.
community
Use when building or running a persistent two-way community space — Discord, Telegram, Circle: platform choice, structure, onboarding, native→bot→human moderation, rituals, growth loops, health metrics. NOT churn of paying product customers (that is retention), NOT broadcast email (that is newsletter), NOT one live…