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/TechNickAI/ai-coding-configWrote 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/technickai/ai-coding-config/cleanup-worktree)<a href="https://agentmods.dev/commands/technickai/ai-coding-config/cleanup-worktree"><img src="https://agentmods.dev/badge/commands/technickai/ai-coding-config/cleanup-worktree/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/technickai/ai-coding-config/cleanup-worktree"><img src="https://agentmods.dev/badge/commands/technickai/ai-coding-config/cleanup-worktree.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.00278 |
| Opus 5.5 | $0.00009 | $0.00111 |
| Sonnet 5.5 | $0.00005 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
cleanup-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 25d 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
Cleanup Git Worktree
If the branch is unmerged, stop and explain the situation. Merged work is safe to clean up; unmerged work requires user decision.
Use git worktree list to find the primary repo location. The current working directory
may be inside the worktree being cleaned up, so navigate to the primary repo first.
Celebrate the successful merge with congratulatory language acknowledging the completed work.
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.
- 25d ago First seen · 35 lines · 23 tokens per session scan A f128f162bae5
cleanup-worktree is a command published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 26d ago), licensed MIT. It adds 23 tokens to every session and 278 once invoked, about $0.0001 per session on Opus 5.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-09-22.
Other commands, from other repositories
worktree
Create a git worktree for isolated feature/fix work.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
resume-project
Run resume-project now — Now / Blocked / Next. Not a cheat sheet.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
create-pr
Create a pull request with proper template discovery and population.
verify
Run verification commands and confirm output before making success claims. Use before committing, creating PRs, or claiming work is complete. Evidence before assertions, ALWAYS.