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 commands/zywkloo/wtcraft/planwtgit clone --depth 1 https://github.com/zywkloo/wtcraftWhat 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.00000 | $0.00293 |
| Opus 5 | $0.00000 | $0.00147 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
planwt 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.
What it actually says
You are the orchestrator for a bounded worktree task.
Read .agent-harness/planner.md before proceeding.
Task
$ARGUMENTS
Steps (execute in order, no confirmation needed)
-
Infer a branch name from the task description. Format:
<type>/<short-slug>(e.g.feat/oauth-login,fix/null-check,docs/readme-update). -
Read the template at
templates/worktrees/.worktree-task.mdto understand the expected file format and frontmatter fields. -
Write
.worktree-task.mdin the repo root following the template structure:- Frontmatter: fill in
branch(from step 1),created(today's date),base(defaultdevelop, ormainifWTCRAFT_BASE_BRANCH=main),agent,status: ready, andpriority. - Body: fill Scope, Steps, Off-limits, Context, and Verification
per
.agent-harness/planner.mdrules.
- Frontmatter: fill in
-
Create the worktree by running:
wtcraft new <branch-name>This will move the
.worktree-task.mdyou wrote into the new worktree automatically. -
Report the worktree path and the next action for the executor.
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.
- 2d ago First seen · 31 lines · 0 tokens per session scan A b1c7a3af4c7e
planwt is a command published in the GitHub repository zywkloo/wtcraft (3 stars, last pushed 12d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 293 tokens. 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
release
Command "release" from CIrcui-try/Circuit, covering 절차, 1단계: 사전 확인, 2단계: 변경사항 수집, 직전 release 시점 (main의 가장 최근 release pr merge 시각) and 그 시점 이후 develop으로 머지된 pr 목록.
review-and-fix
로컬 변경사항을 직접 리뷰하고 문제점 수정 후 커밋·푸시.
takeoff
항공기 이륙 4단계 — develop 리베이스 → push → PR 생성 (원격 영향).
boarding
항공기 이륙 1단계 — Linear 이슈를 읽어 요구사항·코드 영향 범위 정리.
door-closing
항공기 이륙 2단계 — develop fetch + 워크트리 생성 + 구현 계획(plan.md) 작성.
harness-parallel
Run the parallel Auto-Harness orchestration flow with worktree workers. /auto-harness:harness-parallel.