Borrowing it
Nothing to install: this file belongs to dylanroscover/Embody. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dylanroscover/Embody/main/.claude/skills/multi-session-etiquette/SKILL.mdgit clone --depth 1 https://github.com/dylanroscover/EmbodyWrote 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/dylanroscover/embody/multi-session-etiquette)<a href="https://agentmods.dev/skills/dylanroscover/embody/multi-session-etiquette"><img src="https://agentmods.dev/badge/skills/dylanroscover/embody/multi-session-etiquette.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.01537 |
| Opus 5 | $0.00023 | $0.00768 |
| Sonnet 5 | $0.00009 | $0.00307 |
| Haiku 4.5 | $0.00005 | $0.00154 |
Grade A, and why
multi-session-etiquette 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 8d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Session Etiquette
Multiple AI sessions (Claude Code windows, other MCP clients) often work on the same TouchDesigner project at once -- same live network, same externalized files, same git tree. Envoy coordinates them; this rule is how you cooperate.
At session start
Call get_sessions once early. It lists every connected session (label,
idle time, recent_scopes it modified, claims it holds, you = your own
session id). If peers are active, prefer working in a subtree none of them
touched recently.
Read the advisories -- they come to you
- Any tool response may carry
_peers: another session touched territory overlapping your request (op path or externalized file) within ~10 min. conflict: false-- informational. Note it, re-read files before editing them, and avoid building on top of a peer's in-flight work.conflict: true(a peer WROTE there within the last minute) is a HARD STOP. Do not keep mutating that scope. Checkget_sessions, tell the user who is working there, and either divide the work (different subtrees) or get explicit user direction before proceeding.- A
CONFLICT WARNINGorMULTI-SESSION GATEline in_logsfollows the same contract as a LAYOUT WARNING: never end a turn without addressing it.
Claim before big or destructive work
- Before a large build, a refactor of a COMP subtree, or editing an
externalized file, call
claim_scopewith the NARROWEST scope that covers the work and a short note ("rebuilding camera rig"): an op-path prefix (/project1/scene), a file (file:scripts/tools.py), or a special scope (project:testsbefore a test run). - Your own tool calls touching the scope renew the lease automatically; it
expires on its TTL or when your session goes silent.
release_scopewhen done is polite but never required for others to make progress. - If a claim is refused, the response names the holder, their note, and the expiry. Coordinate or work elsewhere -- do NOT retry in a loop.
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.
- 8d ago First seen · 122 lines · 47 tokens per session scan A 592717102134
multi-session-etiquette is a skill published in the GitHub repository dylanroscover/Embody (169 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 1,537 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-30.
Other skills, from other repositories
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
amazon aurora dsql
Deprecated compatibility redirect for Aurora DSQL guidance. Use when a request concerns DSQL, Aurora DSQL, distributed SQL, DSQL schemas, migrations, queries, authentication, performance, or application development.
vibeue
Unreal Engine 5 development using the VibeUE Python API. Use when working in Unreal Engine — blueprints, state trees, materials, actors, landscapes, animation, niagara, widgets, sound, foliage, gameplay tags, enhanced input, skeletons, PCG (procedural content generation), and more. VibeUE is an extension of Unreal's…
testing-python
Write and evaluate effective Python tests using pytest. Use when writing tests, reviewing test code, debugging test failures, or improving test coverage. Covers test design, fixtures, parameterization, mocking, async testing, and CI integration.
issue_analyse_supervisor
Autonomous issue analysis — supervisor delegates to engineer subagents.
algorand-interaction
Interact with Algorand blockchain via the Algorand MCP server — wallet operations, ALGO/ASA transactions, smart contracts, account info, NFD lookups, atomic groups, Tinyman swaps, Haystack Router best-price swaps, Alpha Arcade prediction markets, Pera asset verification, TEAL compilation, knowledge base. Use when user…