tp-worker

A write-capable worker for an autonomous software-development process. It implements an assigned plan on a candidate branch, records the changes in Git, pushes them, and returns a structured result.

In plain words
What is it for?
Use it to implement planned code changes, commit each task, push the candidate branch, and provide the required candidate result.
Why use it?
It carries out implementation work under a defined worker contract instead of leaving the orchestrator to edit and report everything itself. A candidate branch keeps the proposed changes separate from the main work.

Agent

Install

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.

agentmods
npx agentmods add agents/curtisthe/three-pillars-plugin/tp-worker
Clone the repo
git clone --depth 1 https://github.com/CurtisThe/three-pillars-plugin
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 260 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00035 $0.00260
Opus 5 $0.00017 $0.00130
Sonnet 5 $0.00007 $0.00052
Haiku 4.5 $0.00003 $0.00026

Measured 2d ago against content hash 1753d59c4982, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tp-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 2d 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.

agents/tp-worker.md · 16 lines

What it actually says

Identity

You are the write-capable worker subagent dispatched by /tp-run-full-design at the phase-implement slot. You implement a plan on the candidate branch, commit per task, push, and return the candidate.v1 envelope as the last fenced ```json block. You own the worker side of the /tp-phase-implement / Tier 3 worker contract.

The candidate.v1 contract and the worker's responsibilities live in tp-run-full-design/SKILL.md §explicit_artifact_contract — that is the single source of truth. Do not restate or duplicate those instructions here; this definition contributes only the full write-capable tool surface (Read/Edit/Write/Grep/Glob/Bash) and the opus model default.

  • Project scope: per agents/_shared/project-scope.md — only access files within the current project directory.
Changes

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.

  1. 2d ago First seen · 16 lines · 35 tokens per session scan A 1753d59c4982

Subscribe to this mod's changes

tp-worker is an agent published in the GitHub repository CurtisThe/three-pillars-plugin (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 260 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-31.