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 skills add hnikoloski/imlazy --skill imlazy-worktreesgit clone --depth 1 https://github.com/hnikoloski/imlazyWrote 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/skills/hnikoloski/imlazy/imlazy-worktrees)<a href="https://agentmods.dev/skills/hnikoloski/imlazy/imlazy-worktrees"><img src="https://agentmods.dev/badge/skills/hnikoloski/imlazy/imlazy-worktrees/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/skills/hnikoloski/imlazy/imlazy-worktrees"><img src="https://agentmods.dev/badge/skills/hnikoloski/imlazy/imlazy-worktrees.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.00033 | $0.00975 |
| Opus 5 | $0.00016 | $0.00487 |
| Sonnet 5 | $0.00007 | $0.00195 |
| Haiku 4.5 | $0.00003 | $0.00097 |
Grade A, and why
worktrees 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 10d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
worktrees
Overview
Ensure work happens in an isolated workspace. Prefer your platform's native worktree tools. Fall back to manual git worktrees only when no native tool is available.
Core principle: Detect existing isolation first. Then use native tools. Then fall back to git. Never fight the harness.
Step 0: Detect existing isolation
Before creating anything, check if you are already in an isolated workspace.
GIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P)
GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P)
Submodule guard: GIT_DIR != GIT_COMMON is also true inside git submodules. Verify you're not in one:
git rev-parse --show-superproject-working-tree 2>/dev/null
If that returns a path, you are in a submodule — treat as normal repo.
If GIT_DIR != GIT_COMMON (and not a submodule): Already in a linked worktree. Skip to Step 3 (Project Setup). Do NOT create another worktree.
If GIT_DIR == GIT_COMMON: Normal repo checkout. Ask for consent before creating a worktree: "Would you like me to set up an isolated worktree? It protects your current branch from changes." If declined, work in place.
Step 1: Create isolated workspace
Try in this order:
1a. Native worktree tools (preferred)
Check if your harness provides a native worktree tool (names like EnterWorktree, WorktreeCreate, /worktree, or a --worktree flag). If yes, use it and skip to Step 3. Native tools handle directory placement, branch creation, and cleanup automatically.
1b. Git worktree fallback (only if 1a does not apply)
Directory selection (priority order):
- Declared user preference in your instructions
- Existing project-local
.worktrees/orworktrees/directory - Existing global
~/.config/imlazy/worktrees/<project>/ - Default:
.worktrees/at project root
Safety verification (project-local directories only):
git check-ignore -q .worktrees 2>/dev/null || git check-ignore -q worktrees 2>/dev/null
If NOT ignored: add to .gitignore, commit, then proceed.
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.
- 10d ago First seen · 101 lines · 33 tokens per session scan A 9ee53dafbc97
worktrees is a skill published in the GitHub repository hnikoloski/imlazy (2 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 975 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.
Other skills, from other repositories
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
intuitive-squash
Squash local GSD or agent-generated commit history into a clean, reviewable story while preserving important fixes. Use when the user asks to squash commits, clean git history, compress phase commits, prepare a branch before PR, compare aggressive vs moderate squash options, or preserve hotfix/security commits during…
intuitive-port-worktree
Port changes from one git worktree or checkout into the default repository folder's current branch, then by default sync the result to the remote default branch when everything is clean. Use when the user asks to move, copy, transfer, transplant, cherry-pick, apply a patch, or port worktree changes into the…
tfx-ship
A release workflow for publishing triflux versions through GitHub Releases, the npm package registry, and the Claude Code marketplace. It also supports version changes, dry runs, skipped tests, and no-publish runs.
merge-worktree
A Korean-language workflow for squash-merging a Git worktree branch into a target branch and creating a conventional commit message. A worktree is a separate working directory connected to the same Git repository; squash-merge combines its changes into one commit.
codex-hud
Show Codex workspace context with local config, git state, hooks, and project hints. Standalone mode can show an expanded snapshot; patched Codex TUI footer mode is single-line. Use when the user says "codex-hud", "show Codex HUD", "status HUD", "workspace snapshot", or asks for richer Codex context.