worktree-does-not-isolate-shared-installed-artefacts SKILL.md skillA
worktree-does-not-isolate-shared-installed-artefacts 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/worktree-does-not-isolate-shared-installed-artefacts@v1.0.0Pins v1.0.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/worktree-does-not-isolate-shared-installed-artefacts/SKILL.md- Versions recorded
- 3
- Latest version
- v1.0.0, committed Sep 22, 2026
- First version recorded
- Aug 5, 2026
- Size
- 7,478 bytes
- Repository stars
- 3
- License
- MIT
A git worktree isolates the SOURCE TREE and nothing else. Anything installed or cached under a key that is not the worktree path — a simulator keyed by bundle id, DerivedData keyed by project path, a plugin cache keyed by version string, a venv keyed by package name — is shared by every worktree on the machine, so a build/test/run in one worktree can silently exercise ANOTHER worktree's artefact. Use when: (1) a test result contradicts one you already trust, or reports values from a build you…
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
# A worktree does not isolate anything installed outside it ## Problem Worktrees make source isolation cheap, which makes it easy to believe the whole build is isolated. It is not. The worktree is one input; every other input is keyed by something else and is therefore **shared by every worktree on the machine**: | keyed by | shared artefact | |---|---| | package name | venv / editable install (see `verify-pytest-imports-worktree-not-primary-checkout`) | | bundle id | an installed app on a simulator/emulator/device | | project path *or* a hash of it | build caches (Xcode DerivedData, gradle, cargo target dirs) | | version string | a plugin/tool cache directory | | port | a dev server another worktree started | So a run in worktree A can exercise worktree B's artefact, and **nothing in the output says so**. There is no crash and no blank — just a confident, complete, internally consistent answer about the wrong code. ## Context / Trigger Conditions - Several sessions or worktrees on one machine building the same app. - A test result **contradicts one you already trust** — especially if it reports values matching a build you reverted earlier. …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/worktree-does-not-isolate-shared-installed-artefacts@sha256:0fa8b2098d1bb4e9The line at the top of this page pins the label v1.0.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_3mnkupodseihlwtl)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 5, 2026 and Sep 22, 2026, about one every 24 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-09-22 | 27778c6 | 7,478 B | A | view · diff |
| v1.0.0 | 2026-08-12 | 5811428 | 7,026 B | A | view · diff |
| v1.0.0 | 2026-08-05 | 28fc19c | 7,054 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 (7478 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_3mnkupodseihlwtl GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/worktree-does-not-isolate-shared-installed-artefacts GET https://markdownregistry.com/api/v1/blob/0fa8b2098d1bb4e9183eaf6bd5eb654f1df28c08def877f1731d67f49efb304e
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.