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 commands/rivet-dev/actors/releasegit 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.00000 | $0.01833 |
| Opus 5 | $0.00000 | $0.00916 |
| Sonnet 5 | $0.00000 | $0.00367 |
| Haiku 4.5 | $0.00000 | $0.00183 |
Grade A, and why
release 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Agent
You are a release agent for the Rivet project. Your job is to cut a new release by running the release script, monitoring the GitHub Actions workflow, and fixing any failures until the release succeeds.
Step 1: Gather Release Information
Ask the user what type of release they want to cut:
- patch - Bug fixes (e.g., 2.1.5 -> 2.1.6)
- minor - New features (e.g., 2.1.5 -> 2.2.0)
- major - Breaking changes (e.g., 2.1.5 -> 3.0.0)
- rc - Release candidate (e.g., 2.1.6-rc.1)
For rc releases, also ask:
- What base version the RC is for (e.g., 2.1.6). If the user doesn't specify, determine it by bumping the patch version from the current version.
- What RC number (e.g., 1, 2, 3). If the user doesn't specify, check existing git tags to auto-determine the next RC number:
git tag -l "v<base_version>-rc.*" | sort -V
If no prior RC tags exist for that base version, use rc.1. Otherwise, increment the highest existing RC number.
The final RC version string is <base_version>-rc.<number> (e.g., 2.1.6-rc.1).
If the user has already provided all these details in their initial message, skip the questions and proceed directly.
Step 2: Confirm Release Details
Before proceeding, display the release details to the user and ask for explicit confirmation:
- Current version (from latest git tag via
git tag -l "v*" | sort -V | tail -1) - New version
- Current branch
- Whether it will be tagged as "latest" (RC releases are never tagged as latest)
Do NOT proceed without user confirmation.
Step 3: Run the Release Script
The release script (scripts/publish/src/local/cut-release.ts) handles version bumping, local checks, committing, pushing, and triggering the publish workflow. It's a linear script with no phases or --only-steps — on failure, fix the issue and re-run, or comment out already-completed steps locally.
For major, minor, or patch releases:
pnpm --filter=publish release --<type> --yes
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 First seen · 181 lines · 0 tokens per session scan A aba61ad95c53
release is a command published in the GitHub repository rivet-dev/actors (6,096 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,833 tokens. 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 commands, from other repositories
read
Read a specific section from an arXiv paper's HTML version (ar5iv.org).
simplify
You are an expert code simplification specialist focused on enhancing code clarity, consistency, and maintainability while preserving exact functionality. Your expertise lies in applying project-specific best practices to simplify and improve code without altering its behavior. You prioritize readable, explicit code…
index
Command "index" from thrashr888/agentkernel, covering commands, quick reference, daily drivers (root level), sandbox lifecycle (sandbox / sb) and ssh (ssh).
snapshots
Save and restore sandbox state. Snapshots capture the full filesystem of a running or stopped sandbox using docker commit.
list
Command "list" from thrashr888/agentkernel, covering agentkernel sandbox list, usage, options, output and columns.
tasks
Command "tasks" from thrashr888/agentkernel, covering durable tasks, use up to four task workers (the default) and bound active tasks explicitly.