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/commands/mnthe/hardworker-marketplace/teamwork-verify)<a href="https://agentmods.dev/commands/mnthe/hardworker-marketplace/teamwork-verify"><img src="https://agentmods.dev/badge/commands/mnthe/hardworker-marketplace/teamwork-verify.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.00010 | $0.00474 |
| Opus 5 | $0.00005 | $0.00237 |
| Sonnet 5 | $0.00002 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
teamwork-verify 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 8d 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 Verify Command
Overview
Manually trigger final verification for a teamwork project. Spawns a final-verifier teammate to perform comprehensive checks on the entire project.
Step 1: Check Project State
Use TaskList to verify there are completed tasks to check:
tasks = TaskList()
# Count completed vs total tasks
If no completed tasks:
No completed tasks found. Nothing to verify.
Use /teamwork-status to check progress.
Step 2: Spawn Final Verifier
ACTION REQUIRED - Call Task tool with:
- subagent_type: "teamwork:final-verifier"
- model: "opus"
- prompt:
Task: Run final verification for the project. Please verify the entire project, checking for: - All tasks completed with evidence - No file conflicts between tasks - Full project build succeeds - Test suite passes - No blocked patterns in changed files - Cross-task dependencies satisfied Use TaskList to review all tasks and their status. Use Read and Bash to verify build/test results. Report your findings with a clear PASS or FAIL verdict.
Wait for verifier to complete.
Step 3: Display Verification Result
# Verification Result
## Verdict
{PASS or FAIL}
## Summary
{verifier's findings}
## Details
- Tasks checked: {count}
- Build: {PASS/FAIL}
- Tests: {passed}/{total}
- Issues: {list or "None"}
## Next Steps
{If PASS: "Project verified. Ready for delivery."}
{If FAIL: "Issues found. Review details above and fix."}
Usage Examples
# Run final verification
/teamwork-verify
# After fixing issues, re-verify
/teamwork-verify
Integration with Workflow
| Scenario | Action |
|---|---|
| All tasks complete | Run /teamwork-verify |
| Verification fails | Fix issues, then re-run |
| Before PR/delivery | Run for final quality check |
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.
- 8d ago First seen · 99 lines · 10 tokens per session scan A b242871d607f
teamwork-verify is a command published in the GitHub repository mnthe/hardworker-marketplace (4 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 474 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.