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 task-executiongit 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/task-execution)<a href="https://agentmods.dev/skills/agentscope-ai/agentteams/task-execution"><img src="https://agentmods.dev/badge/skills/agentscope-ai/agentteams/task-execution/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/task-execution"><img src="https://agentmods.dev/badge/skills/agentscope-ai/agentteams/task-execution.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.00058 | $0.02072 |
| Opus 5.5 | $0.00023 | $0.00829 |
| Sonnet 5.5 | $0.00012 | $0.00414 |
| Haiku 4.5 | $0.00006 | $0.00207 |
Grade A, and why
teamharness-task-execution 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 today.
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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Execution
Use this skill when executing assigned work as a Worker or remote member.
Claim only tasks assigned to you. Read the task spec, keep deliverables in the task directory, ask focused blocker questions, and submit a structured result.
Do not change project-level state or project result files.
Do not use this skill or taskflow for readiness checks, direct questions, or explicit requests to reply with specific text. Answer those directly in the current room.
Task Directory
Your assigned task lives under:
shared/tasks/{task-id}/
Your Leader owns:
shared/tasks/{task-id}/meta.json
shared/tasks/{task-id}/spec.md
You own:
shared/tasks/{task-id}/workspace/
shared/tasks/{task-id}/progress/
shared/tasks/{task-id}/result.md
Do not edit:
shared/projects/{project-id}/meta.json
shared/projects/{project-id}/plan.md
shared/projects/{project-id}/result.md
If a task spec asks you to write or submit shared/projects/..., report that
boundary conflict to the Leader. Put Worker-owned deliverables under
shared/tasks/{task-id}/...; your Leader owns project-level reports.
Acknowledge
When you are mentioned with TASK_ASSIGNED, first pull or inspect the task
directory if needed, then acknowledge with taskflow:
{
"role": "worker",
"action": "ack_task",
"payload": {
"taskId": "demo-project-001-01"
}
}
If ack_task fails because the task is missing or assigned elsewhere, stop and
report the blocker to the Leader in the current room. Do not invent task files.
Read:
shared/tasks/{task-id}/spec.md
before doing the work.
Execute
Keep all deliverables under the task directory. If you need private notes, use:
shared/tasks/{task-id}/workspace/
Use meaningful filenames for deliverables. Prefer names that describe the
artifact's purpose, such as analysis.md, trace-summary.log, or
patch-notes.md; avoid vague names like output.md when there are multiple
files.
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.
- today Changed · +26 lines 8e89fc70a971
- 1mo ago Changed · +5 lines 0b4924cb741b
- 1mo ago Changed · +41 lines · +3 tokens per session 7d228fbc033e
- 2mo ago First seen · 160 lines · 55 tokens per session scan A 36483b626ac9
teamharness-task-execution is a skill published in the GitHub repository agentscope-ai/AgentTeams (5,887 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 2,072 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
add-linear
Add Linear channel integration via Chat SDK. 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.
standup-summary
Tell Gemma what you did, what you're working on, and any blockers. Get a clean standup update.