driver-test-runner

A test-running procedure for RivetKit drivers, checking each test-file group on both native and WebAssembly runtimes.

In plain words
What is it for?
Use it to check a driver after changes, bring up a new driver, or work through failures systematically across supported runtimes.
Why use it?
It keeps track of which tests have run, reducing the risk of skipping cases while validating changes or investigating failures.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/rivet-dev/actors/driver-test-runner
Any agent
npx skills add rivet-dev/actors --skill driver-test-runner
Clone the repo
git clone --depth 1 https://github.com/rivet-dev/actors

Made for: Claude Code, Codex.

Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,699 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00068 $0.03699
Opus 5 $0.00034 $0.01850
Sonnet 5 $0.00014 $0.00740
Haiku 4.5 $0.00007 $0.00370

Measured yesterday against content hash 63049087cf11, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

driver-test-runner scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sf http://127.0.0.1:6420/health || echo "NOT RUNNING"
.claude/skills/driver-test-runner/SKILL.md · 321 lines

How it starts

The opening of the file, as written. The whole thing — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Driver Test Suite Runner

Methodically run the RivetKit driver test suite one file group at a time across the native (NAPI) and wasm runtimes, tracking progress in ~/.agents/notes/driver-test-progress.md.

Arguments

The skill accepts optional arguments:

  • reset — Clear progress and start from the beginning.
  • resume — Pick up from where we left off (default behavior).
  • only <file> — Run only a specific test file group (e.g., only actor-conn).
  • from <file> — Start from a specific file group, skipping earlier ones.
  • runtime <native|wasm|both> — Which runtime(s) to run (default: both).
  • encoding <bare|cbor|json> — Override encoding (default: bare).
  • registry <static> — Override registry type (default: static).

Runtime Matrix

The driver suite runs over a runtime × SQLite-backend × encoding matrix defined in rivetkit-typescript/packages/rivetkit/tests/driver/shared-matrix.ts. The runtime dimension has two values:

  • native — NAPI bindings (@rivetkit/rivetkit-napi). Pairs with sqlite=local for the primary native driver pass.
  • wasm — WebAssembly bindings (@rivetkit/rivetkit-wasm). Wasm cannot use local SQLite; it must pair with sqlite=remote (executes SQL through the engine over the wire).

The skill defaults to running each test file twice: once on native/local and once on wasm/remote, each at encoding=bare. A file is checked off only when both runtimes pass.

The test harness does not read environment variables for matrix selection. Always select matrix cells with Vitest -t using the full inner describe name: runtime (<runtime>) / sqlite (<backend>) / encoding (<encoding>).

How It Works

0. Anchor the reference before fixing parity bugs

If a RivetKit driver test fails because native or Rust behavior diverges from the old runtime, do this before inventing a separate debugging workflow:

  1. Treat rivetkit-typescript/packages/rivetkit driver tests as the primary oracle.
  2. Compare the failing behavior against the original TypeScript implementation at ref feat/sqlite-vfs-v2 using git show or git diff.
  3. Patch native/Rust to match the original TypeScript behavior.
  4. Rerun the same TypeScript driver test before adding any lower-level native tests.

Read the full file on GitHub · 321 lines

Changes

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.

  1. yesterday First seen · 321 lines · 68 tokens per session scan A 63049087cf11

Subscribe to this mod's changes

driver-test-runner is a skill published in the GitHub repository rivet-dev/actors (6,096 stars, last pushed 3d ago), licensed Apache-2.0. It adds 68 tokens to every session and 3,699 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.