Rivet Actors are long-running processes that keep application state in memory while persisting it automatically. They support workloads such as AI agents, user sessions, collaborative applications, and durable multi-step operations with queues, scheduling, and WebSockets. Catalogue add-ons help operate and develop Rivet Actors.
Borrowing it
Nothing to install: this file belongs to rivet-dev/actors. 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/rivet-dev/actors/main/.claude/skills/stack-merge/SKILL.mdgit clone --depth 1 https://github.com/rivet-dev/actorsWrote 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/rivet-dev/actors/stack-merge)<a href="https://agentmods.dev/skills/rivet-dev/actors/stack-merge"><img src="https://agentmods.dev/badge/skills/rivet-dev/actors/stack-merge/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/rivet-dev/actors/stack-merge"><img src="https://agentmods.dev/badge/skills/rivet-dev/actors/stack-merge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 85 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00157 | $0.02214 |
| Opus 5.5 | $0.00063 | $0.00886 |
| Sonnet 5.5 | $0.00031 | $0.00443 |
| Haiku 4.5 | $0.00016 | $0.00221 |
Grade A, and why
stack-merge 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 1mo 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stack Merge
Land an entire Graphite downstack into main in one admin-bypass fast-forward push, then close every in-scope PR explicitly. No per-PR CI gates, no merge commits on main, no gh pr merge per PR. PRs end up in Closed state (not MERGED) unless their base was already main, but their commits are in main's history.
This skill replaces Graphite's merge queue — use when you want the outcome Graphite's queue produces (linear history, all PRs merged) but without waiting for the queue. Requires admin bypass on main branch protection.
When NOT to use
- User wants normal single-PR merge → use
gh pr merge. - User isn't a repo admin → push will reject (tell them to use Graphite's queue).
- Stack tip has failing CI and user cares → queue would refuse; pause here too.
Preconditions (verify at start; bail early)
- Admin/bypass on main:
gh api repos/rivet-dev/rivet/branches/main/protection— check user is inbypass_pull_request_allowances.users[]or has repo admin. If not, stop. - Graphite initialized:
gt lssucceeds. - Clean working tree:
git status --shortempty. In-flight rebase/merge state must be resolved first. - Worktree sanity:
git worktree list— prune anyprunableentries withgit worktree prune. Stale worktrees break rebases with "already checked out at" errors. See references/gotchas.md.
The flow (8 phases)
Each phase has a validation gate or confirmation gate. Writes happen only after the user explicitly approves the final commands.
Phase 1 — Scope
Input: target branch name from user.
- Enumerate the merge path: walk
gh pr view <branch> --json baseRefNamefrom target down tomain. Produces the ordered list of all PRs that will be closed in Phase 8. - Do not infer parents from
gt lsvisual order — use each PR'sbaseRefName. See gotchas.md. - Script:
scripts/list_merge_path.sh <target-branch>.
Phase 2 — Sync
gt sync --no-interactive. Pulls latest main, cleans up merged upstream branches.- Read output for any
(needs restack)markers in the merge path.
What ships with it
6 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.
- 1mo ago First seen · 138 lines · 157 tokens per session scan A f0c3b6cbad81
stack-merge is a skill published in the GitHub repository rivet-dev/actors (6,309 stars, last pushed yesterday), licensed Apache-2.0. It adds 157 tokens to every session and 2,214 once invoked, about $0.0006 per session on Opus 5.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
codex-pr-body
Update the title and body of one or more pull requests.
update-v8-version
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-close-issues
Close resolved Codewhale issues only after verifying the landed commit/behavior, with a positive crediting comment; never from title alone.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.