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/adrielp/ai-engineering-harness/worktreegit clone --depth 1 https://github.com/adrielp/ai-engineering-harnessWhat 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.00851 |
| Opus 5 | $0.00000 | $0.00426 |
| Sonnet 5 | $0.00000 | $0.00170 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
worktree 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Worktree Manager
Conventions
Branch naming:
- Ticket path → strip dir +
.md, prefixfeature/:thoughts/shared/tickets/add-auth.md→feature/add-auth - Plain name → prefix
feature/unless already prefixed (fix/,chore/, etc.)
Worktree location: <repo-root>/../<repo-name>-worktrees/<branch-name> (sibling dir, outside main repo)
Default branch detection — never hardcode main:
DEFAULT_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's|refs/remotes/origin/||') || DEFAULT_BRANCH="main"
Subcommand Dispatch
Parse the first argument. If none provided, print:
/worktree create <name|ticket-path> — Create worktree + branch
/worktree list — All worktrees with dirty status
/worktree status — Detailed view (commits, ahead/behind)
/worktree remove <name> — Remove with safety checks
Examples:
/worktree create auth-refactor
/worktree create thoughts/shared/tickets/add-auth.md
create
-
Resolve branch name using naming conventions above. If argument is a ticket path, read the ticket for context.
-
Check conflicts — run in parallel:
git branch --list "<branch-name>" git worktree listIf branch exists but has no worktree → offer
git worktree add <path> <existing-branch>(no-b). If worktree already exists at path → show its location, ask if user wants tocdthere instead. -
Create:
REPO_ROOT=$(git rev-parse --show-toplevel) REPO_NAME=$(basename "$REPO_ROOT") WORKTREE_PATH="$REPO_ROOT/../${REPO_NAME}-worktrees/<branch-name>" mkdir -p "$(dirname "$WORKTREE_PATH")" git worktree add "$WORKTREE_PATH" -b <branch-name> -
Output: Branch, path, base ref,
cdcommand. If from ticket, include ticket path.
list
Quick overview of all worktrees.
git worktree list --porcelain
Porcelain format — each worktree is a block separated by blank lines:
worktree /path/to/dir
HEAD <sha>
branch refs/heads/<name>
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 · 107 lines · 0 tokens per session scan A 4a479f6654ba
worktree is a command published in the GitHub repository adrielp/ai-engineering-harness (20 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 851 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.