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.
/plugin marketplace add mnthe/hardworker-marketplace/plugin install teamworkWrote 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/commands/mnthe/hardworker-marketplace/teamwork-worker)<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>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.00012 | $0.00865 |
| Opus 5 | $0.00006 | $0.00432 |
| Sonnet 5 | $0.00002 | $0.00173 |
| Haiku 4.5 | $0.00001 | $0.00086 |
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.
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
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.
- 7d ago First seen · 129 lines · 12 tokens per session scan A 18db2fe922b7
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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.