Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add mvschwarz/openrig --skill seat-continuity-and-handovergit clone --depth 1 https://github.com/mvschwarz/openrigWrote 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/mvschwarz/openrig/seat-continuity-and-handover)<a href="https://agentmods.dev/skills/mvschwarz/openrig/seat-continuity-and-handover"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/seat-continuity-and-handover/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mvschwarz/openrig/seat-continuity-and-handover"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/seat-continuity-and-handover.svg" alt="Reviewed on agentmods" width="80" 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.00087 | $0.01863 |
| Opus 5 | $0.00044 | $0.00932 |
| Sonnet 5 | $0.00017 | $0.00373 |
| Haiku 4.5 | $0.00009 | $0.00186 |
Grade A, and why
seat-continuity-and-handover 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 yesterday.
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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Seat Continuity and Handover
A pair of primitive families that separate who is sitting in a seat from what the seat itself is:
- Occupant-creation primitives —
resume,fork,rebuild,fresh— produce a candidate new occupant. Answer: "where did the new occupant come from?" - Seat-binding operations — handover binds a candidate occupant into the topology. Answer: "what happened to the stable seat identity?" Inspect the current CLI for executable operations; design vocabulary alone does not establish a command.
Core architectural decision: stable seat identity, fluid occupant identity, explicit provenance. Do not encode successive occupants into live seat names. Keep the stable address and record lineage separately.
Use this when
- Replacing a seat's occupant via rebuild, fork, fresh, or seat-handover
- Choosing old-occupant disposition: retire / advise / shadow
- Reasoning about whether a seat's lineage is stable or has drifted
- Reading or writing the provenance record for a seat
- Designing or auditing topology stability across an occupant change
Don't use this when
- The seat is freshly created (no occupant to replace) — use
rig launch/rig expanddirectly - The intent is to change topology shape (add/remove seats), not replace an occupant — use topology-mutation primitives
The two-outcome honesty model
Every seat-binding operation produces two independent outcomes:
continuityOutcome: rebuilt | resumed | forked | fresh | failed
seatBindingOutcome: handed_over | partial | failed | unchanged
These can disagree honestly. Examples:
continuityOutcome: failed+seatBindingOutcome: unchanged— new occupant didn't materialize; seat correctly retains old occupant.continuityOutcome: rebuilt+seatBindingOutcome: failed— candidate created OK; bind failed mid-flight; provenance records the gap.
Don't collapse these into one outcome. The system can describe what actually happened only if the two are recorded independently.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · +6 lines afa4b29aa17e
- 10d ago First seen · 152 lines · 87 tokens per session scan A 6b5163e6f2a7
seat-continuity-and-handover is a skill published in the GitHub repository mvschwarz/openrig (66 stars, last pushed yesterday), licensed Apache-2.0. It adds 87 tokens to every session and 1,863 once invoked, about $0.0004 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
dynamic-resources
Example skill loaded from resourcesdiscover.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…
bundle-safety
Bundle transform safety — minification variant selection, consumer-constraint verification, identifier preservation, and namespace re-export coverage for build output.
run-test-suite-after-registration-changes
When delegating a task affected by this skill, include.