AgentTeams is a runtime platform where multiple AI agents collaborate in shared Matrix rooms under the coordination of a manager. It is for human-supervised or enterprise workflows that need visible, auditable cooperation among agents running on different runtimes, with shared files and centralized traffic management.
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 agentscope-ai/AgentTeams --skill project-participationgit clone --depth 1 https://github.com/agentscope-ai/AgentTeamsWrote 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/agentscope-ai/agentteams/project-participation)<a href="https://agentmods.dev/skills/agentscope-ai/agentteams/project-participation"><img src="https://agentmods.dev/badge/skills/agentscope-ai/agentteams/project-participation/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/agentscope-ai/agentteams/project-participation"><img src="https://agentmods.dev/badge/skills/agentscope-ai/agentteams/project-participation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.00316 |
| Opus 5 | $0.00020 | $0.00158 |
| Sonnet 5 | $0.00008 | $0.00063 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
project-participation 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.
What it actually says
Project Participation
Gotchas
- Project plan is auto-synced — read directly from
~/shared/projects/{project-id}/plan.md - Git author must be your worker name — set
git config user.nameanduser.emailbefore any commits - Report completion via @mention to your coordinator — this is what advances the project to the next task
Project Context
When invited to a Project Room, the project plan is already available locally (auto-synced):
cat ~/shared/projects/{project-id}/plan.md
The plan.md shows:
- All project tasks, their status (
[ ]pending /[~]in-progress /[x]completed) - Which tasks are yours and what dependencies exist
- Links to task brief and result files for each task
Workflow
- When assigned a task in the project room, mark it as started in your memory
- Execute the task following normal task execution flow
- Report completion via @mention to your coordinator so the project can advance
Git Config for Projects
Use your worker name as Git author so contributions are identifiable:
git config user.name "<your-worker-name>"
git config user.email "<your-worker-name>@agentteams.local"
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 · 41 lines · 40 tokens per session scan A 450196206d9d
project-participation is a skill published in the GitHub repository agentscope-ai/AgentTeams (5,584 stars, last pushed 4d ago), licensed Apache-2.0. It adds 40 tokens to every session and 316 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-30.
Other skills, from other repositories
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
slack-construct-agents
Standing context for Slack sibling agents — one room per team, creator-posted introductions, bot-to-bot hop discipline. Ships as instructions.md composed into the group's CLAUDE.md at spawn; there is no workflow to invoke.
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
multi-agent
A process for coordinating multiple coding agents by splitting work among scouts, workers, reviewers, and repair agents. Each agent has a defined role and task.
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is…