main-bash-cwd-persists-nested-worktree SKILL.md skillA
main-bash-cwd-persists-nested-worktree from wan-huiyan/agent-traffic-control is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wan-huiyan/agent-traffic-control/main-bash-cwd-persists-nested-worktree@v1.2.0Pins v1.2.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wan-huiyan/agent-traffic-control
- Path
plugins/agent-traffic-control/skills/main-bash-cwd-persists-nested-worktree/SKILL.md- Versions recorded
- 3
- Latest version
- v1.2.0, committed Jul 8, 2026
- First version recorded
- May 29, 2026
- Size
- 11,827 bytes
- Repository stars
- 3
- License
- MIT
Prevent and diagnose nested git worktrees created at the wrong filesystem path when orchestrating parallel work from the main Claude Code agent. Use when (1) you ran `git worktree add .claude/worktrees/<name> ...` from the main agent's Bash tool, (2) `git worktree list` shows the new worktree at an unexpected nested path like `.claude/worktrees/<previous-worktree>/.claude/worktrees/<name>` instead of the intended top-level location, (3) a subagent dispatched to the intended path…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Main-agent Bash cwd persistence → nested worktrees at wrong path ## Problem You're orchestrating multiple parallel-dispatch subagents, each in its own git worktree. From the main agent's Bash tool you do: ```bash git worktree add .claude/worktrees/track-A origin/main -b feat/track-A # ... dispatch Track A subagent ... # ... investigate codebase ... cd /path/to/repo/.claude/worktrees/track-A && grep -rn "foo" src/ # persists cwd! # ... time passes, you dispatch Track B ... git worktree add .claude/worktrees/track-B origin/main -b feat/track-B ``` You expect `track-B` at `<repo>/.claude/worktrees/track-B`. Instead `git worktree list` reports it at `<repo>/.claude/worktrees/track-A/.claude/worktrees/track-B` — nested inside the Track A worktree. Branches, commits, and pushes still work (git resolves them via `.git/worktrees/<name>` metadata regardless of disk location), but: - Dispatched subagents pointed at the intended path will report "worktree path mismatch." - Cleanup (`git worktree remove .claude/worktrees/track-B`) from the project root won't find it. - Per-worktree caches, venvs, and uploads end up under the wrong parent directory. ## Context / Trigger conditions …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/main-bash-cwd-persists-nested-worktree@sha256:1fc2fa44b1b6605cThe line at the top of this page pins the label v1.2.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_j6chx5hywem45sxk)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between May 29, 2026 and Jul 8, 2026, about one every 20 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.2.0 latest | 2026-07-08 | b0f0d02 | 11,827 B | A | view · diff |
| v1.2.0 | 2026-07-08 | f1254dd | 11,839 B | A | view · diff |
| v1.0.0 | 2026-05-29 | 059688a | 6,628 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11827 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wan-huiyan/agent-traffic-control · 3 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_j6chx5hywem45sxk GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/main-bash-cwd-persists-nested-worktree GET https://markdownregistry.com/api/v1/blob/1fc2fa44b1b6605cd237412bad6137f5a2928526c5b0e4fdc644e83907e3c316
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.