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 agentmods add skills/mvschwarz/openrig/session-source-forknpx skills add mvschwarz/openrig --skill session-source-forkgit clone --depth 1 https://github.com/mvschwarz/openrigWhat 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 | $0.00110 | $0.02143 |
| Opus 5 | $0.00055 | $0.01071 |
| Sonnet 5 | $0.00022 | $0.00429 |
| Haiku 4.5 | $0.00011 | $0.00214 |
Grade A, and why
session-source-fork 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 2d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
session_source Fork
session_source is a member-level OpenRig field that declares how a
newly-launched managed seat should derive its initial conversation
continuity from a prior runtime conversation source.
v1 supports one mode: fork — start a new managed seat from a
prior native runtime conversation source without claiming the original
seat continued.
The schema is runtime-neutral; implementation is runtime-specific (Claude and Codex have their own native fork commands).
Use this when
- Authoring a rig spec member that should fork from a prior session
- Authoring a
rig expandpayload withsession_source - Reasoning about whether to use
forkvsrebuildvsresumevsfreshfor a new seat - Composing fork + handover (seat-handover-over-fork) — see
seat-continuity-and-handoverskill
Don't use this when
- The seat is being restored, not created. Restore continues an existing managed seat. Fork creates a new seat.
- The continuity is artifact-backed mental-model rebuild (packet-derived understanding, not native runtime continuity). Use
mode: rebuild(seeseat-continuity-and-handoverfor the rebuild surface) — do NOT collapse fork into artifact-backed reentry; the distinction is load-bearing. - The runtime is
terminal. Terminal runtime rejectssession_source.
The shape (canonical YAML)
members:
- id: reviewer-2
runtime: claude-code # or "codex"; not valid on terminal
agent_ref: specs/agents/reviewer.yaml
profile: reviewer
cwd: .
session_source:
mode: fork
ref:
kind: native_id # v1 fork mode supports native_id only
value: "0b0165d7-cb4d-4650-90de-15c0a1ede9e6"
Rules:
modev1 only valid value:fork.ref.kindv1 supportsnative_idonly. Schema rejectsartifact_path,name,last, andartifact_setpre-launch with explicit deferred/weaker/wrong-mode error messages (seepackages/daemon/src/domain/rigspec-schema.tsvalidateSessionSourceFork). Adapter-level refusal exists as defensive handling but should not be reachable in v1 because schema rejects first.valuerequired forref.kind: native_idin v1 (the only schema-accepted kind). Future-state value semantics forartifact_path/name/lastare not active in v1 because schema rejects those kinds pre-launch.rig expandaccepts the same shape so dynamically-added members can carry session-source attribution.
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.
- 2d ago First seen · 161 lines · 110 tokens per session scan A 80b5f8dce680
session-source-fork is a skill published in the GitHub repository mvschwarz/openrig (64 stars, last pushed 2d ago), licensed Apache-2.0. It adds 110 tokens to every session and 2,143 once invoked, about $0.0006 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
autoprompt
Explicit-only useful-first orchestration. Invoke only when the user names autoprompt - typed as /autoprompt or in plain language such as "act in autoprompt mode" - to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Do not infer invocation from…
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.
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.
ap-feature-coordinator
L1 feature coordinator - drives approved ROADMAP.md lanes through their required build/review/verification gates and owns the run-wide feature frontier.
ap-implementer
L3 executor - G4 IMPLEMENT. Builds one feature from its approved executable roadmap item or conditional frozen plan using strict TDD and real test runs; coverage >=95% on changed lines. Reports PLAN-CONFLICT rather than improvising.
ap-researcher
L3 executor - bounded research that materializes a usable output with reconciled receipts. Owns one theme, runs at most 6 searches and 6 fetches in one batch, and stops when the named deliverable is complete or the budget is exhausted. Does not spawn.