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-delegationgit 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-delegation)<a href="https://agentmods.dev/skills/agentscope-ai/agentteams/task-delegation"><img src="https://agentmods.dev/badge/skills/agentscope-ai/agentteams/task-delegation/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-delegation"><img src="https://agentmods.dev/badge/skills/agentscope-ai/agentteams/task-delegation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 88 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00059 | $0.01871 |
| Opus 5.5 | $0.00024 | $0.00748 |
| Sonnet 5.5 | $0.00012 | $0.00374 |
| Haiku 4.5 | $0.00006 | $0.00187 |
Grade A, and why
teamharness-task-delegation 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 1mo 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Delegation
Use this skill when acting as Leader to create Project Work task specs, send assignment messages, and check submitted Worker results.
Each delegated task should have a task id, owner, scope, expected deliverables, acceptance criteria, and blocker reporting path. Write task instructions to the shared task directory before asking the owner to execute.
A submitted result is only a candidate result until accepted by the Leader. Do not use this skill to turn ordinary conversation into tasks.
Scope
Use this skill for:
taskflowcalls as Leader- converting a ready project node into a Worker task spec
- checking a submitted Worker result
- routing task assignment and completion messages
Use teamharness-project-management to create projects, plan DAG or Loop work,
resolve ready nodes, record Loop iteration decisions, and accept results into
project progress.
Delegate Only Ready Nodes
Use delegate_task only for Project Work nodes that are ready in project
state. Do not create bare tasks directly from a user request. First create or
update a project DAG, then delegate a ready project node returned by
projectflow readyNodes, or create/update a Loop and delegate a ready
project node returned by readyLoopNodes.
For Quick Task, projectflow create_quick_project is used instead. It
already writes shared/tasks/{task-id}/meta.json,
shared/tasks/{task-id}/spec.md, and marks the task assigned; do not call
delegate_task again for that task. create_quick_project does not
auto-notify, so after it returns ok: true, send the assignment message
described in the Assignment Message section below.
Before delegation:
- Resolve the Worker Matrix ID or stable member name from the team roster.
- Confirm the node came from
readyNodesorreadyLoopNodes. - Write a bounded task spec through
taskflow. The spec must include the completion report instruction below. - Keep Worker deliverables under
shared/tasks/{task-id}/.... Do not ask a Worker to write or submitshared/projects/...; project reports are Leader owned. - Use the current Matrix Task room for the assignment. Do not fall back to the requester/source session.
delegate_taskmentions the assigned Worker automatically after it succeeds — do not send a second mention.
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.
- 1mo ago Changed · +10 lines · +3 tokens per session 7b328b72519d
- 1mo ago First seen · 197 lines · 56 tokens per session scan A f9fd750fb91b
teamharness-task-delegation is a skill published in the GitHub repository agentscope-ai/AgentTeams (5,825 stars, last pushed yesterday), licensed Apache-2.0. It adds 59 tokens to every session and 1,871 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.
review-offered-task
Turn prompt for an offered swarm task: read the offer, accept with task-action and start work-on-task, or reject with a reason.