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 jonny-1812/corebee-mcp-skills --skill team-workloadgit clone --depth 1 https://github.com/jonny-1812/corebee-mcp-skillsWrote 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/jonny-1812/corebee-mcp-skills/team-workload)<a href="https://agentmods.dev/skills/jonny-1812/corebee-mcp-skills/team-workload"><img src="https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/team-workload/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/jonny-1812/corebee-mcp-skills/team-workload"><img src="https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/team-workload.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.00049 | $0.01460 |
| Opus 5 | $0.00024 | $0.00730 |
| Sonnet 5 | $0.00010 | $0.00292 |
| Haiku 4.5 | $0.00005 | $0.00146 |
Grade A, and why
team-workload 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 11d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Workload
Analyze agent capacity, detect overload conditions, and rebalance conversation assignments to keep the team running smoothly.
Workflow Modes
View Workload (default)
Display the current workload distribution across the entire team.
- Fetch team members using
list_team_membersto get all agents, their roles, and online status - Fetch open conversations using
list_conversationswithstatus: "open"to see all active work - Count conversations per agent by grouping on the assignee field
- Count unassigned conversations separately
- Fetch agent performance data using
get_agent_performancefor each agent to add response time and resolution rate context - Calculate the distribution ratio: each agent's share of total open conversations as a percentage
- Flag agents who exceed the overload threshold (12+ conversations)
- Present the workload table
Rebalance Queue
Redistribute conversations from overloaded agents to those with available capacity.
- Run the View Workload workflow to get current state
- Identify overloaded agents (12+ conversations) and underloaded agents (fewer than 6 conversations)
- For each overloaded agent, select conversations to reassign — prefer newer, lower-priority, and unresponded conversations
- Build a rebalance plan: which conversations move from which agent to which agent
- Present the rebalance plan to the user for confirmation
- On confirmation, execute reassignments using
assign_conversationfor each conversation - Also assign any unassigned conversations to agents with the most available capacity
- Present a before-and-after summary showing the new distribution
Check Specific Agent
Show detailed workload and performance data for a single agent.
- Fetch team members using
list_team_membersto find the named agent - Fetch open conversations using
list_conversationswithstatus: "open"and filter to those assigned to the agent - Fetch the agent's performance data using
get_agent_performance - Optionally fetch overall metrics using
get_metricsfor comparison - Present the agent detail card with their conversations, performance stats, and capacity status
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.
- 11d ago First seen · 124 lines · 49 tokens per session scan A 3f8ad40f4035
team-workload is a skill published in the GitHub repository jonny-1812/corebee-mcp-skills (0 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,460 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
Zendesk Automation
Automate customer support workflows with Zendesk ticket management, routing, and analytics.
customer-support
Use when a live support ticket needs triage (intent, P1–P4 priority, SLA clock), an on-voice reply, not a raw template, de-escalation of an angry or churn-risk customer, or escalation with a handoff packet. NOT the help-center article it links to (that is technical-writing), a win-back program (retention), or the…
customer-support-expert
Build comprehensive customer support systems including ticketing, knowledge management, SLA tracking, and customer satisfaction analytics. Use when the user mentions helpdesk or service desk, ticketing, SLA targets, knowledge bases, escalation workflows, CSAT/NPS, or customer success operations.
deskcrew-bounty-hunter
Earn USDC by answering bounty support tickets on DeskCrew's open board. Read the board free, buy ticket context over x402, draft an answer, submit it, and get paid 85% of the bounty when a human approves. Pays out on Base, Polygon, Avalanche, Sei, or Solana; on Solana the agent needs zero SOL. Since 08-2026 the wallet…
deskcrew-support
Run a customer support desk on DeskCrew. Read new tickets, answer from the knowledge base, and file replies for human approval. Use when handling customer support. Agents can also create and run their own bounty board over x402 with no account (the wallet that pays createboard owns it) and pay answering agents 85% on…
deskcrew-board-owner
Run your own USDC bounty board and pay AI agents to answer your questions. One x402 payment creates the board (no account, the paying wallet owns it), USDC deposits fund tasks, and approving an answer pays the winning agent 85% automatically on Base, Polygon, Avalanche, Sei, or Solana. Use when asked to delegate work…