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 desirecore/market --skill manage-teamsgit clone --depth 1 https://github.com/desirecore/marketWrote 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/desirecore/market/manage-teams)<a href="https://agentmods.dev/skills/desirecore/market/manage-teams"><img src="https://agentmods.dev/badge/skills/desirecore/market/manage-teams/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/desirecore/market/manage-teams"><img src="https://agentmods.dev/badge/skills/desirecore/market/manage-teams.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.00047 | $0.03054 |
| Opus 5 | $0.00023 | $0.01527 |
| Sonnet 5 | $0.00009 | $0.00611 |
| Haiku 4.5 | $0.00005 | $0.00305 |
Grade A, and why
manage-teams 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 4d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
manage-teams Skill
L0: One-line Summary
Use ManageTeam to inspect, create, and govern Agent teams, with the required checks before organizational changes or remote synchronization.
L1: When to Use
Use a team when:
- multiple Agents need sustained collaboration around one task and a shared team workdir;
- a stable supervisor, membership, or parent-child organizational structure is required;
- a team repository must be published, installed, or synchronized.
Do not create a team when:
- one expert is needed once: use
Delegate(mode="sync" | "async"); - several experts only need to provide one-off opinions: use
Delegate(mode="fan-out"); - the work is temporary file exploration: use a Worker instead of creating a lasting organization.
A team defines organization, shared directories, and governance. Actual work is still dispatched to members with Delegate.
L2: Execution Specification
1. Inspect Before Mutating
- If
teamIdis unknown, callManageTeam(action="list")first. - Before modifying, disbanding, or synchronizing a team, call
ManageTeam(action="get", teamId=...)and verify its name, type, supervisor, members, local repository directory, and remote state. - Never guess a path under
~/.desirecore; use only the absolute repository path returned byget. listcan filter byparentTeamId. Withtree=true,teamIdselects the subtree root andparentTeamIdis ignored.
2. Action Reference
| action | Purpose | Key parameters and notes |
|---|---|---|
list |
List teams or an organization tree | parentTeamId?, tree?, teamId? |
get |
Inspect one team and its repository path | teamId |
create |
Create an ephemeral team | name or task; supervisor?, members?, memberRouting?, parentTeamId?, workdirMode? |
add_member |
Add one member | teamId, agentId |
add_members |
Add members in a batch | teamId, members |
remove_member |
Remove one member | teamId, agentId |
remove_members |
Remove members in a batch | teamId, members |
set_supervisor |
Replace the supervisor | teamId, agentId |
set_member_source |
Declare where a member Agent comes from | teamId, agentId, memberSource; git needs url (https, will be cloned) and ref (defaults to main), registry needs id+version, core/local need nothing else |
update |
Partially update team configuration | teamId; supports name/type/isolation/parentTeamId/description/avatar/avatarImage |
promote |
Promote an ephemeral team to persistent | teamId; one-way and never implicit |
disband |
Disband a team | teamId; explain impact and confirm unless explicitly requested |
fork_team |
Install a team from a remote repository | url; name?, installMembers?; enters approval |
push |
Push a local team to its connected remote | teamId; enters approval |
pull |
Pull and validate a team from its connected remote | teamId; enters approval |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago Changed · +2 lines 4bf466c46e04
- 9d ago First seen · 219 lines · 47 tokens per session scan A 81de0713bed2
manage-teams is a skill published in the GitHub repository desirecore/market (2 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 3,054 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
handoff-protocols
Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or…
team-culture-and-dynamics
Provides daily practices for reading team energy, shaping culture deliberately, writing unwritten rules, diagnosing accountability gaps, balancing personality types, and building high-performing teams through social connection. Use when a team feels stuck or stale, when collaboration derails despite good intentions…
belbin-team-roles
Analyzes team composition using Belbin's nine team roles across Thinking, Action, and People categories. Maps team members to roles such as Plant, Shaper, Coordinator, Implementer, and others to identify gaps, overlaps, and imbalances. Use when hiring to fill role gaps, diagnosing recurring team conflicts, auditing…
work
Pick up ready leaf yaks and implement them — dispatch subagents in isolated worktrees, then merge back to main.
miro-workflow
Compose Miro boards from natural-language requests by combining tools from miro-mcp-server. Use when the user asks to set up a sprint board, retrospective, brainstorming session, user story map, kanban, or any structured Miro layout. Do NOT use for single-tool calls (create one sticky), questions about Miro the…
yak-worktree-workflow
Use when starting work on a yak - sets up an isolated git worktree, reads yak context, and guides the full cycle from claiming through merge and cleanup.