worktree-outer-ls-mistaken-for-main-state SKILL.md skillA
worktree-outer-ls-mistaken-for-main-state 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-outer-ls-mistaken-for-main-state@v1.1.0Pins v1.1.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-outer-ls-mistaken-for-main-state/SKILL.md- Versions recorded
- 3
- Latest version
- v1.1.0, committed Aug 11, 2026
- First version recorded
- May 13, 2026
- Size
- 12,060 bytes
- Repository stars
- 3
- License
- MIT
Prevent citing files as "on main" when they actually live only in a sibling worktree's working tree. Use when (1) you're working inside a worktree at `<repo>/.claude/worktrees/<X>/` and need to verify whether a file or feature is on `origin/main`, (2) you're tempted to run `ls /path/to/outer-repo/...` or `find /path/to/outer-repo` to check, (3) you're about to cite that filesystem-walk result in a PR description, handoff doc, or commit message as if it represented main's state. Trap: in a…
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
# Worktree: Outer-`ls` Mistaken for Main-State ## Problem You're working inside a git worktree at `<repo>/.claude/worktrees/<branch>/`. You need to verify whether some file (e.g., `docs/handoffs/session_184_X.md`) exists on `origin/main` — perhaps because: - You're writing a handoff doc and want to cite "the canonical S184 prompt that's already on main" - You're filing a PR body and want to confirm the file you're referencing actually exists - You're cross-checking a claim from MEMORY.md against current main The natural-feeling check is: ```bash ls /Users/.../repo/docs/handoffs/ | grep session_184 # → session_184_drivers_breakdown_full_sweep_prompt.md ``` You walk up out of the worktree, list the outer repo's `docs/handoffs/`, see the file, and cite it as "on main". **That conclusion is wrong** in any repo with multiple worktrees in use. ## Context / Trigger Conditions All four must be true to fire this trap: 1. The repo has **2+ active worktrees** (`git worktree list` shows >1 entry) 2. You're cwd-anchored inside one worktree (e.g., `.claude/worktrees/<X>/`) 3. You need to verify a claim about `origin/main`'s state …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/worktree-outer-ls-mistaken-for-main-state@sha256:d3f657726b858fc4The line at the top of this page pins the label v1.1.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_iilotlaawluilo66)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between May 13, 2026 and Aug 11, 2026, about one every 45 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-08-11 | f274e4b | 12,060 B | A | view · diff |
| v1.1.0 | 2026-07-08 | f1254dd | 12,062 B | A | view · diff |
| v1.0.0 | 2026-05-13 | 07472bf | 9,608 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 (12060 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_iilotlaawluilo66 GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/worktree-outer-ls-mistaken-for-main-state GET https://markdownregistry.com/api/v1/blob/d3f657726b858fc4c9c3c871d3adce47acb09f787e4c6a907f4f17651853b69a
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.