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/using-teammates)<a href="https://agentmods.dev/skills/andreymudri/claude-teammates/using-teammates"><img src="https://agentmods.dev/badge/skills/andreymudri/claude-teammates/using-teammates/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/using-teammates"><img src="https://agentmods.dev/badge/skills/andreymudri/claude-teammates/using-teammates.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.00035 | $0.01287 |
| Opus 5 | $0.00017 | $0.00643 |
| Sonnet 5 | $0.00007 | $0.00257 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
using-teammates 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Teammates
This is the entrypoint. Read it before doing anything else this session — including answering a question, exploring the codebase, or checking a file.
The Rule
Invoke relevant skills BEFORE any response or action — including clarifying questions, exploring the codebase, or checking files.
Then announce "Using [skill] to [purpose]" and follow the skill exactly.
Skill Priority
Process skills set the approach; implementation skills carry it out. When both apply, the process skill goes first.
- "Let's build X" →
brainstormingfirst, then implementation skills. - "Fix this bug" →
systematic-debuggingfirst, then domain skills.
Routing
| Situation | Skill |
|---|---|
| Exploring an idea, unclear requirements, before any design or plan | brainstorming |
| Requirements are settled and a multi-step change needs a written plan | writing-plans |
| A written plan exists and there's a git repo with 3+ disjoint tasks — run a fleet | parallel-execution |
| A written plan exists but the work doesn't warrant a fleet — work it inline | executing-plans |
| A bug, test failure, or unexpected behavior, before proposing a fix | systematic-debugging |
| Implementing any feature or bugfix, before writing implementation code | test-driven-development |
| Feedback came back on your work, before acting on it | receiving-code-review |
| Implementation is complete and all tests pass — decide how to integrate | finishing-a-development-branch |
| Creating or editing a skill, or verifying one works before deployment | writing-skills |
| Spawn, list, message, scale, stop, or resume teammates in a running fleet | fleet-lifecycle |
| Changing how the fleet runs — parallelism, model tier or effort per role, caveman output | teammates-config |
| A fleet phase finished and needs a verdict before the next phase starts | phase-gate |
| Want to know what a running fleet is doing right now | fleet-supervision |
Fleet or Solo
A fleet is eligible when all of these hold:
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 · 120 lines · 35 tokens per session scan A add05482a939
using-teammates is a skill published in the GitHub repository andreymudri/claude-teammates (2 stars, last pushed 8d ago), licensed MIT. It adds 35 tokens to every session and 1,287 once invoked, about $0.0002 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
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.
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…