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/rivet-dev/actors/stack-mergenpx skills add rivet-dev/actors --skill stack-mergegit clone --depth 1 https://github.com/rivet-dev/actorsWhat 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.00157 | $0.02214 |
| Opus 5 | $0.00078 | $0.01107 |
| Sonnet 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 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 — 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.
- 2d 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,096 stars, last pushed 4d ago), licensed Apache-2.0. It adds 157 tokens to every session and 2,214 once invoked, about $0.0008 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
lint-js
Lint JS/TS code only. Use before opening a PR when only JavaScript or TypeScript files were changed (no Rust).
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
test
Detect the project’s test stack, run the narrowest useful tests, create tests when authorized, and report coverage/gaps honestly.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).