cassini-workshop: Skill for Claude Code

.claude/skills/agent-teams/SKILL.md

agent-teams is a skill for Claude Code from opagani/cassini-workshop. It costs 161 tokens per session (1,520 once invoked), scanned A, a copy of agent-teams, MIT.

A guide for coordinating multiple Claude Code sessions as teammates. Each teammate works in a separate session and can take responsibility for part of a larger task.

In plain words
What is it for?
Use it for multi-file refactors, reviews, audits, or other projects that can be split into separate workstreams. It also explains how the lead session delegates work and waits for results.
Why use it?
It helps divide independent work so several parts can progress at the same time. Shared tasks and direct messages make it easier to coordinate the results.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

This is opagani/cassini-workshop's own configuration. It tells Claude Code how to work on cassini-workshop itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything cassini-workshop configures →

Reuse

Borrowing it

Nothing to install: this file belongs to opagani/cassini-workshop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/opagani/cassini-workshop/main/.claude/skills/agent-teams/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/opagani/cassini-workshop

Made for: Claude Code.

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.

agentmods badge for agent-teams

README.md
[![agentmods](https://agentmods.dev/badge/skills/opagani/cassini-workshop/agent-teams.svg)](https://agentmods.dev/skills/opagani/cassini-workshop/agent-teams)
Your own site
<a href="https://agentmods.dev/skills/opagani/cassini-workshop/agent-teams"><img src="https://agentmods.dev/badge/skills/opagani/cassini-workshop/agent-teams.svg" alt="Measured on agentmods" height="20"></a>
Per session 161 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,520 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00161 $0.01520
Opus 5 $0.00081 $0.00760
Sonnet 5 $0.00032 $0.00304
Haiku 4.5 $0.00016 $0.00152

Measured 7d ago against content hash 7b46acb8ca37, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

agent-teams scanned grade A with 1 finding 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 7d 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.

Reads agent configuration directorieslowAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

// ~/.claude/settings.json

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Origin

This is a copy

100% identical to agent-teams — 0 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.

.claude/skills/agent-teams/SKILL.md · 135 lines

How it starts

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

Agent Teams orchestration

Claude Code's experimental Agent Teams coordinates multiple Claude Code sessions. The session that creates the team is the lead (you, here); teammates are separate sessions with their own full context windows that message each other directly and pull work off a shared task list.

This differs from subagents (the Agent tool): subagents run inside one session and only report back to their parent. Teammates are peers — they coordinate through a shared mailbox and task list, and self-claim work.

The one rule this skill exists to enforce

Delegate and wait. Do not implement the parallel work yourself in the lead session. When a task decomposes into independent streams, the lead's job is to spawn teammates, assign/seed tasks, monitor, and synthesize — not to write module A then module B then the tests sequentially. If you catch yourself doing the work, stop and delegate it.

  • ❌ Anti-pattern: "Write the auth module, then the API, then the tests" → lead does all three in order.
  • ✅ Pattern: spawn 3 teammates (auth / API / tests), assign clear tasks, then wait for all to finish before synthesizing.

If asked to proceed and teammates aren't done: do not start doing their work — wait, or steer them.

Preflight — is it enabled?

Agent Teams is off by default and needs Claude Code v2.1.32+. It requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 (env or settings.json env). If a request clearly wants a team but the feature may be off, check first and tell the user how to enable it rather than silently falling back to doing everything solo:

// ~/.claude/settings.json
{
  "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" },
  "teammateMode": "auto"   // "auto" | "in-process" | "tmux"
}

teammateMode: auto (split panes if in tmux, else in-process), in-process (cycle with Shift+Down), tmux (needs tmux/iTerm2; one pane per teammate). Per-session override: claude --teammate-mode in-process. Teammate model is set via /config → "Default teammate model" (does not inherit /model).

Read the full file on GitHub · 135 lines

Files

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.

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.

  1. 7d ago First seen · 135 lines · 161 tokens per session scan A 7b46acb8ca37

Subscribe to this mod's changes

agent-teams is a skill published in the GitHub repository opagani/cassini-workshop (0 stars, last pushed 2mo ago), licensed MIT. It adds 161 tokens to every session and 1,520 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). It is 100% identical to agent-teams, differing in 0 lines, and is treated as a copy.