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.
git clone --depth 1 https://github.com/mnthe/hardworker-marketplaceWrote 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/plugins/mnthe/hardworker-marketplace/teamwork)<a href="https://agentmods.dev/plugins/mnthe/hardworker-marketplace/teamwork"><img src="https://agentmods.dev/badge/plugins/mnthe/hardworker-marketplace/teamwork/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/plugins/mnthe/hardworker-marketplace/teamwork"><img src="https://agentmods.dev/badge/plugins/mnthe/hardworker-marketplace/teamwork.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
teamwork 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 1mo 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
{
"name": "teamwork",
"version": "3.4.1",
"skills": "./skills/",
"description": "Native teammate-based collaboration plugin with role-based workers, event-driven coordination, and Claude Code agent teams.",
"author": {
"name": "mnthe"
},
"keywords": [
"teamwork",
"collaboration",
"agent-teams",
"role-based",
"workers",
"task-management",
"parallel",
"native-api",
"cross-platform"
],
"license": "MIT",
"commands": "./commands/",
"agents": [
"./agents/backend/AGENT.md",
"./agents/devops/AGENT.md",
"./agents/docs/AGENT.md",
"./agents/final-verifier/AGENT.md",
"./agents/frontend/AGENT.md",
"./agents/orchestrator/AGENT.md",
"./agents/review/AGENT.md",
"./agents/security/AGENT.md",
"./agents/test/AGENT.md",
"./agents/worker/AGENT.md"
]
}
What it installs
The manifest is a name and a version. 4 skills, 5 commands travel with it, and installing the plugin installs all of them — 190 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill task-decomposition A 33 tokens
- Skill worker-workflow A 44 tokens
- Skill event-coordination A 28 tokens
- Skill teamwork-clean A 34 tokens
- Command teamwork A 12 tokens
- Command teamwork-worker A 12 tokens
- Command teamwork-status A 9 tokens
- Command teamwork-verify A 10 tokens
- Command teamwork-clean A 8 tokens
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.
- 1mo ago First seen · 35 lines scan A 948d09130a82
teamwork is a plugin published in the GitHub repository mnthe/hardworker-marketplace (4 stars, last pushed 6mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills own folder layout and templates; /obw:pm splits a spec into blocking tickets; /issue is a Claude Mod pane that lists a view of the project's dashboard, draws Mermaid as text diagrams, and can open a card in the browser through viz.…
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested PR or MR with agents.
mission-control
SDLC management for Operations, Asgard, and CAMPPS: prepared issue drafts, live schema sync, board schemas, labels, project fields, metrics, and card validation.
feishu-calendar
Manage Feishu (Lark) calendar events — create, read, update, delete events and manage attendees via the Feishu Open Platform Calendar API v4.
gse
GSE-One — AI engineering companion for structured SDLC management. 24 commands, adaptive risk analysis, unified backlog, knowledge transfer, worktree isolation.