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 superset-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/superset-fleet)<a href="https://agentmods.dev/skills/larcane97/clausona/superset-fleet"><img src="https://agentmods.dev/badge/skills/larcane97/clausona/superset-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/superset-fleet"><img src="https://agentmods.dev/badge/skills/larcane97/clausona/superset-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.00123 | $0.02924 |
| Opus 5.5 | $0.00049 | $0.01170 |
| Sonnet 5.5 | $0.00025 | $0.00585 |
| Haiku 4.5 | $0.00012 | $0.00292 |
Grade A, and why
superset-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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Superset fleet on clausona profiles
superset:orchestrate (in Claude Code) or superset-orchestrate (in Codex) is the protocol: a
coordinator table, one workspace per task, worker briefs that end in a SUPERSET_WORKER_DONE or
SUPERSET_WORKER_BLOCKED envelope, monitoring and follow-ups. Load it and follow it. fleet-core
holds the clausona rules: which profile runs each worker, launch arguments, limits, judging,
retiring and the report. This skill adds the Superset steps.
0. Load the shared rules
Load the fleet-core skill first and follow it. 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. Reaching Superset
Stop and tell the user what is missing if any of these fails.
superset:orchestrate(Claude Code) orsuperset-orchestrate(Codex) is available.- Choose how to reach Superset:
- If
superset auth whoamisucceeds, use the CLI path: thesupersetcommands below, as orchestrate does. Check a command's--helpbefore its first use, because the CLI changes quickly. - Otherwise use the helper path.
node <base>/scripts/superset-host.mjs statusmust print"ok": true.- The helper calls the Superset host service on this machine with the token from its manifest, and never prints the token.
- Every helper command prints JSON.
- If it says the host API has changed, stop and pass that message on.
- If
Below, H means node <base>/scripts/superset-host.mjs. H trust, H terminals wait,
H terminals read --source transcript and H workspaces delete are used on both paths.
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 Changed · +19 lines 20212db346c4
- 16d ago Changed · -107 lines · +5 tokens per session 2638da176d6d
- 19d ago First seen · 260 lines · 118 tokens per session scan A c1c0be16f9a7
superset-fleet is a skill published in the GitHub repository larcane97/clausona (57 stars, last pushed 5d ago), licensed MIT. It adds 123 tokens to every session and 2,924 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-07.
Other skills, from other repositories
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.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
requirements-writer
Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
refocusing
Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.
orchestration-team
Use when coordinating assignments, selected review boundaries, or blocked work across a rig.
oversight-team
Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention…