session-handoff-number-collision-with-unmerged-sibling SKILL.md skillA
session-handoff-number-collision-with-unmerged-sibling 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/session-handoff-number-collision-with-unmerged-sibling@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/session-handoff-number-collision-with-unmerged-sibling/SKILL.md- Versions recorded
- 4
- Latest version
- v1.1.0, committed Aug 12, 2026
- First version recorded
- May 13, 2026
- Size
- 16,470 bytes
- Repository stars
- 3
- License
- MIT
Detect and recover from a session-number collision when running session-handoff and a parallel/sibling session has authored a same-numbered handoff doc that hasn't merged into main yet. Use when: (1) you're in `session-handoff` Phase 1 about to write `docs/handoffs/session_NNN_handoff.md`, (2) `ls docs/handoffs/` shows the highest number is N-1 (so you pick N), BUT (3) MEMORY.md "Recent sessions" or sessions_archive.md already contains a `session_NNN_*.md` entry pointing at another worktree's…
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
# Session-Handoff Number Collision With Unmerged Sibling ## Problem `session-handoff` Phase 1 Step 2 says "Write handoff doc → `docs/handoffs/session_N_handoff.md`." The implicit assumption is that you can determine N by inspecting `docs/handoffs/` on the current branch. **This assumption breaks when a parallel/sibling session ran concurrently in another worktree and its handoff PR hasn't merged into main yet.** Concrete sequence: 1. Sibling session ran 2 hours ago in `.claude/worktrees/other/`, drafted `session_167_handoff.md`, opened PR #690 (still under review). 2. Sibling session updated MEMORY.md "Recent sessions" with an S167 entry AND appended to sessions_archive.md. 3. You fork your worktree off `origin/main` — MEMORY.md is local-user-state so you see the sibling's S167 entry, but `docs/handoffs/` on `origin/main` does NOT yet have `session_167_handoff.md` (PR pending). 4. You run `ls docs/handoffs/` → highest is S166b → you pick **S167**. 5. You write `docs/handoffs/session_167_handoff.md` + `session_168_prompt.md`. …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/session-handoff-number-collision-with-unmerged-sibling@sha256:254a4b55df71220cThe 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_bvpxtbmepgq5fvm4)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 13, 2026 and Aug 12, 2026, about one every 30 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-08-12 | f461c97 | 16,470 B | A | view · diff |
| v1.1.0 | 2026-08-05 | e3930cf | 16,106 B | A | view · diff |
| v1.1.0 | 2026-07-08 | f1254dd | 16,201 B | A | view · diff |
| v1.1.0 | 2026-05-13 | 07472bf | 15,968 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 (16470 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_bvpxtbmepgq5fvm4 GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/session-handoff-number-collision-with-unmerged-sibling GET https://markdownregistry.com/api/v1/blob/254a4b55df71220c56304955aa55a09ba5808fba355e00afef94ef77466ff762
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.