Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add andreymudri/claude-teammates/plugin install claude-teammatesWrote 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/andreymudri/claude-teammates/fleet-supervision)<a href="https://agentmods.dev/skills/andreymudri/claude-teammates/fleet-supervision"><img src="https://agentmods.dev/badge/skills/andreymudri/claude-teammates/fleet-supervision/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/andreymudri/claude-teammates/fleet-supervision"><img src="https://agentmods.dev/badge/skills/andreymudri/claude-teammates/fleet-supervision.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.00028 | $0.01524 |
| Opus 5 | $0.00014 | $0.00762 |
| Sonnet 5 | $0.00006 | $0.00305 |
| Haiku 4.5 | $0.00003 | $0.00152 |
Grade A, and why
fleet-supervision 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 10d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fleet Supervision
Digest
node "$CLAUDE_PLUGIN_ROOT/scripts/cli.mjs" digest --run <runId> --root <project root>
Show that block as-is. It is deliberately compact; do not expand it into prose.
What the repository says
node "$CLAUDE_PLUGIN_ROOT/scripts/cli.mjs" doctor --run <runId> --plan <planPath> --root <project root>
The digest renders status.json, which the teammates being supervised write; doctor asks git
instead. It reports the main worktree's branch and any dirty paths, every worktree and who holds
it, and per task the branch tip and what it actually contributes from its own fork point. Exit 1
means it found problems, all named — a branch with no changes (the work landed on another ref), a
worktree inside the repository, a branch that reached the base branch without the run branch.
Run it after a teammate returns and before a gate. It decides nothing and records nothing: a
teammate is done on the strength of this report and the gate, never on its own say-so.
Event-driven, not polling
Background teammates notify on completion — react to those notifications. The only timer is a long heartbeat (20-30 minutes) to catch a teammate that hangs and never notifies. Do not sit in a poll loop.
The heartbeat
node "$CLAUDE_PLUGIN_ROOT/scripts/cli.mjs" liveness --run <runId> --plan <planPath> --root <project root>
Run it on the 20-30 minute heartbeat, not in a loop. Exit 1 means at least one teammate of the current phase has neither committed nor touched its worktree inside the window.
Exit 2 means it did not measure what you asked about, and is neither a stall nor an all-clear. Fix what the message names and run it again. It reports that when:
- no current phase can be named — the main worktree is on the base branch, the plan is missing at the anchor, or the phases integrated out of order;
- the run id matches no run directory (a typo would otherwise report a board of "not started");
- the plan in the working tree has no task in the derived phase, which an amendment mid-run causes;
- a row reads
unknown, meaning freshness was not measured for that teammate. Two causes, and the output names which: no worktree of that branch could be read — none is registered, because the teammate was dispatched without worktree isolation or is working in the main worktree — or the walk hit its 5000-entry cap, for which the fix is to add the generated directory to the project .gitignore, since the walk skips what git ignores.
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.
- 10d ago First seen · 116 lines · 28 tokens per session scan A ae8b14f60891
fleet-supervision is a skill published in the GitHub repository andreymudri/claude-teammates (2 stars, last pushed 8d ago), licensed MIT. It adds 28 tokens to every session and 1,524 once invoked, about $0.0001 per session on Opus 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-08-31.
Other skills, from other repositories
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.