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-status)<a href="https://agentmods.dev/commands/mnthe/hardworker-marketplace/teamwork-status"><img src="https://agentmods.dev/badge/commands/mnthe/hardworker-marketplace/teamwork-status/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/commands/mnthe/hardworker-marketplace/teamwork-status"><img src="https://agentmods.dev/badge/commands/mnthe/hardworker-marketplace/teamwork-status.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.00009 | $0.00561 |
| Opus 5 | $0.00005 | $0.00280 |
| Sonnet 5 | $0.00002 | $0.00112 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
teamwork-status 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 9d 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.
What it actually says
Teamwork Status Command
Overview
Display a dashboard-style status view of a teamwork project. Uses native TaskList for live task status and project-status.js for project metadata.
Step 1: Parse Arguments
Parse options:
--project NAME: Override project detection--team NAME: Override sub-team detection
Detect project/team:
# Default detection
PROJECT=$(basename "$(git rev-parse --show-toplevel 2>/dev/null)" || echo "unknown")
SUB_TEAM=$(git rev-parse --abbrev-ref HEAD 2>/dev/null | tr '/' '-' || echo "main")
# Check for overrides in arguments
Step 2: Gather Status Data
Option A: Use project-status.js for project metadata
bun "${CLAUDE_PLUGIN_ROOT}/src/scripts/project-status.js" --project "${PROJECT}" --team "${SUB_TEAM}" --format table
Option B: Use native TaskList for live task status
tasks = TaskList()
# Parse task list for status counts
Combine both sources for a comprehensive dashboard.
If project doesn't exist:
Error: Project not found: {PROJECT}/{SUB_TEAM}
Start a project with: /teamwork "your goal"
Step 3: Display Dashboard
# Teamwork Status
## Project
- Name: {PROJECT}
- Sub-team: {SUB_TEAM}
- Goal: {goal}
## Progress
{completed}/{total} tasks ({percentage}%)
| Status | Count |
|--------|-------|
| Completed | {n} |
| In Progress | {n} |
| Pending | {n} |
| Blocked | {n} |
## Tasks
| ID | Task | Status | Owner |
|----|------|--------|-------|
| 1 | ... | completed | worker-backend |
| 2 | ... | in_progress | worker-frontend |
| 3 | ... | pending | - |
## Commands
- /teamwork-worker Start a worker
- /teamwork-verify Run verification
- /teamwork-clean Clean up project
Options Reference
| Option | Description |
|---|---|
--project NAME |
Override project name (default: git repo name) |
--team NAME |
Override sub-team name (default: branch name) |
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.
- 9d ago First seen · 98 lines · 9 tokens per session scan A 7247379f1b10
teamwork-status is a command published in the GitHub repository mnthe/hardworker-marketplace (4 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 561 once invoked, about $0.0000 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.