teamwork-worker

teamwork-worker is a command for Claude Code from mnthe/hardworker-marketplace. It costs 12 tokens per session (865 once invoked), scanned A, original, MIT.

A command for joining an existing teamwork project as a worker teammate. It reads the project’s tasks and can choose a role automatically or use one you specify.

In plain words
What is it for?
Use it to join a project, select or detect a worker role, find assigned tasks, and complete them through the project’s task and messaging tools.
Why use it?
It removes the need to find the project context and decide which worker role to use manually. It also reports an error when the requested project does not exist.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the teamwork plugin — 4 skills, 5 commands shipped together

Good fit Use it to join a project, select or detect a worker role, find assigned tasks, and complete them through the project’s task and messaging tools.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add mnthe/hardworker-marketplace
Claude Code
/plugin install teamwork

Made for: Claude Code.

Or install teamwork, the plugin that ships this one along with the rest of its 4 skills, 5 commands.

Wrote 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.

agentmods badge for teamwork-worker

README.md
[![agentmods](https://agentmods.dev/badge/commands/mnthe/hardworker-marketplace/teamwork-worker.svg)](https://agentmods.dev/commands/mnthe/hardworker-marketplace/teamwork-worker)
Your own site
<a href="https://agentmods.dev/commands/mnthe/hardworker-marketplace/teamwork-worker"><img src="https://agentmods.dev/badge/commands/mnthe/hardworker-marketplace/teamwork-worker.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 865 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.00865
Opus 5 $0.00006 $0.00432
Sonnet 5 $0.00002 $0.00173
Haiku 4.5 $0.00001 $0.00086

Measured 7d ago against content hash 18db2fe922b7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

teamwork-worker 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 7d 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.

plugins/teamwork/commands/teamwork-worker.md · 129 lines

How it starts

The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Teamwork Worker Command

Overview

Join an existing teamwork project as a worker teammate. The worker uses native teammate API (TaskList, TaskUpdate, SendMessage) to find and complete tasks.

Automatic Role Detection: When --role is not specified, the worker reads available tasks from project metadata and selects the appropriate role-specific agent.

Role Selection Precedence: --role flag (explicit) > task.role (auto-detected) > "worker" (generic fallback)


Step 1: Read Project Metadata

Read project metadata to verify the project exists and get context:

bun "${CLAUDE_PLUGIN_ROOT}/src/scripts/project-status.js" --project "${PROJECT}" --team "${SUB_TEAM}" --format json

Parse options from arguments:

  • --project NAME: Override project detection (default: git repo name)
  • --team NAME: Override sub-team detection (default: branch name)
  • --role ROLE: Specify worker role

If project doesn't exist:

Error: No teamwork project found for: {PROJECT}/{SUB_TEAM}

Start a project with: /teamwork "your goal"

Step 2: Spawn Worker Agent as Teammate

Determine agent type using precedence order:

# Precedence: user --role > default 'worker'
if user_specified_role:
    subagent_type = f"teamwork:{user_specified_role}"
else:
    subagent_type = "teamwork:worker"

Valid role values: frontend, backend, test, devops, docs, security, review, worker

ACTION REQUIRED - Call Task tool with:

  • subagent_type: {subagent_type} (determined using logic above)
  • team_name: {project}-{sub_team} (join existing team)
  • name: worker-{role}
  • prompt:
    PROJECT: {project}
    SUB_TEAM: {sub_team}
    ROLE: {role or "any"}
    
    You are a worker teammate. Use native API to find and complete tasks:
    
    1. TaskList() to find available tasks
    2. TaskUpdate(taskId, owner="worker-{role}", status="in_progress") to claim
    3. Implement the task using Read, Write, Edit, Bash
    4. TaskUpdate(taskId, status="completed") when done
    5. SendMessage to orchestrator with completion summary
    

Read the full file on GitHub · 129 lines

Changes

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.

  1. 7d ago First seen · 129 lines · 12 tokens per session scan A 18db2fe922b7

Subscribe to this mod's changes

teamwork-worker is a command published in the GitHub repository mnthe/hardworker-marketplace (4 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 865 once invoked, about $0.0001 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.