2,231 mods in this category, of every kind an agent can take.
Each one carries what it costs per session, what the scan found, and
whether it is the original.
Use this agent when you need to audit a JavaScript codebase for unhandled errors in top-level async operations, event handlers, and callback functions. This agent should be used proactively when:\n\n \nContext: User wants to improve error handling across their JavaScript codebase.\nuser: "Can you check if we're…
Use this agent when the user needs to write, modify, or debug driver tests for RivetKit. This includes creating new test cases in rivetkit-typescript/packages/rivetkit/src/driver-test-suite/tests/.ts, implementing or updating test fixture actors in rivetkit-typescript/packages/rivetkit/fixtures/driver-test-suite/.ts…
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.
Create and publish concise Rivet launch or changelog posts through an approval-gated workflow, including release research, a required user-selected hero variation, local HTML-rendered social and technical images, an R2 hero upload, MDX authoring, a reviewed draft GitHub PR for manual merge, and a scheduled and…
Creates accessible hand-authored inline SVG architecture and sequence diagrams for documentation. Use when adding, replacing, or reviewing docs diagrams, especially Mermaid flowcharts.
Methodically run the RivetKit driver test suite file by file across the native (NAPI) and wasm runtimes, tracking progress in /.agents/notes/driver-test-progress.md. Use when you need to validate the driver test suite after changes, bring up a new driver, or debug test failures systematically.
AGENTS.md instructions for rivet-dev/actors, a project described as: Rivet Actors are the primitive for stateful workloads. Built for AI agents, collaborative apps, and durable execution.
AGENTS.md instructions for Dicklesworthstone/destructive_command_guard, covering agents.md — dcg (destructive command guard), rule 0 - the fundamental override prerogative, rule number 1: no file deletion, git branch: only use main, never master and toolchain: rust & cargo.
Copilot instructions for agentgateway/agentgateway: Do not check for, speculate about, or report compilation errors during code review. Compilation diagnostics from review are frequently incorrect; rely on CI to detect and report compilation failures.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers.…
Analyze and improve code quality for any path in the monorepo. Use whenever the user asks to improve, audit, review, clean up, refactor, lint, or check code quality for a directory or file. Also trigger for requests about security review, performance optimization, robustness checks, dependency audits, or readability…
Claude Code instructions for moonrepo/moon, a project described as: A build system and monorepo management tool for the web ecosystem, written in Rust.
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time when it should be cached, or when outputs are empty or missing after a…
Claude Code instructions for sonos/tract, covering before you commit, commit messages, inline comments, doc comments (/// / //!) and how to change a model.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: