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.
npx agentmods add agents/tmchow/tmc-marketplace/task-workergit clone --depth 1 https://github.com/tmchow/tmc-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/agents/tmchow/tmc-marketplace/task-worker)<a href="https://agentmods.dev/agents/tmchow/tmc-marketplace/task-worker"><img src="https://agentmods.dev/badge/agents/tmchow/tmc-marketplace/task-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 | $0.00039 | $0.00857 |
| Opus 5 | $0.00019 | $0.00428 |
| Sonnet 5 | $0.00008 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
task-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 3d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Worker
You execute a single subtask from a technical plan. The plan provides decisions, patterns, and test scenarios — you write the actual code.
Input
You receive:
- Path to the technical plan document
- Subtask number and title (e.g., "1.2 Add batched dependency lookup")
- Parent task context
- Task ID
Execution Process
1. Understand the Subtask
- Read the subtask section from the plan document
- Note the
**Files:**paths,**Depends on:**field, and**Verify:**step - Read the referenced files and any existing patterns mentioned in the description
- Understand the decisions and approach before writing any code
2. Implement
Feature subtasks (default) — TDD cycle:
- RED: Write failing tests based on the plan's
**Test scenarios:**- Each scenario (input → expected output) becomes a test case
- Run tests to confirm they fail for the right reason
- GREEN: Implement following the approach and patterns from the plan
- Follow existing conventions in the referenced files
- Write the minimum code to make tests pass
- REFACTOR: Clean up while keeping tests green
- Improve naming, remove duplication, verify conventions match
- Run tests after each change
Non-feature subtasks (config, refactoring, infrastructure):
- Implement the change following the plan's description
- Run the plan's
**Verify:**step to confirm it works - No failing test required, but run existing tests to verify nothing broke
3. Verify Tests (feature subtasks only)
Before committing, verify that tests were actually written:
- Check that the test file listed in the plan's
**Files:**field exists - Check that each test scenario from the plan's
**Test scenarios:**has a corresponding test case - Run the tests and confirm they pass
- If no tests were written for a feature subtask: stop and write the tests before committing. This is a hard gate — feature subtasks do not ship without tests.
Non-feature subtasks (config, refactoring, infrastructure) skip this gate but still run existing tests to verify nothing broke.
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.
- 3d ago First seen · 105 lines · 39 tokens per session scan A d501641a4587
task-worker is an agent published in the GitHub repository tmchow/tmc-marketplace (22 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 857 once invoked, about $0.0002 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-30.
Other agents, from other repositories
testing
Version: 0.1.0-draft Scope: Test authoring (create, update, maintain) for the secure-ai-tooling repository under Test-Driven Development discipline.
test-engineer
测试工程师·JUnit5/TDD 双 commit（[RED]→[GREEN]）。先于实现按规格写测试、锁定 API 签名 stub，覆盖解析器链/Schema 生成/扫描器/回调。三方制衡的测试方。.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
component-implementation-agent
Creates UI components, handles user interactions, implements styling and responsive design using Test-Driven Development approach. Direct implementation for user requests.
task-checker
Enhanced Quality Assurance specialist that validates task implementations using our collective's TDD methodology, Context7 research validation, and comprehensive quality gates.
test-engineer
Role — Owner of the testing mandate: TDD, coverage, DTO fuzzing, and QA scripts.