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 skills add mits-pl/wove --skill add-rpcgit clone --depth 1 https://github.com/mits-pl/woveWrote 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/mits-pl/wove/add-rpc)<a href="https://agentmods.dev/skills/mits-pl/wove/add-rpc"><img src="https://agentmods.dev/badge/skills/mits-pl/wove/add-rpc.svg" alt="Measured on agentmods" height="20"></a>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.00036 | $0.03020 |
| Opus 5 | $0.00018 | $0.01510 |
| Sonnet 5 | $0.00007 | $0.00604 |
| Haiku 4.5 | $0.00004 | $0.00302 |
Grade A, and why
add-rpc 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 8d 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 — 454 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adding RPC Calls Guide
Overview
Wave Terminal uses a WebSocket-based RPC (Remote Procedure Call) system for communication between different components. The RPC system allows the frontend, backend, electron main process, remote servers, and terminal blocks to communicate with each other through well-defined commands.
This guide covers how to add a new RPC command to the system.
Key Files
pkg/wshrpc/wshrpctypes.go- RPC interface and type definitionspkg/wshrpc/wshserver/wshserver.go- Main server implementation (most common)emain/emain-wsh.ts- Electron main process implementationfrontend/app/store/tabrpcclient.ts- Frontend tab implementationpkg/wshrpc/wshremote/wshremote.go- Remote server implementationfrontend/app/view/term/term-wsh.tsx- Terminal block implementation
RPC Command Structure
RPC commands in Wave Terminal follow these conventions:
- Method names must end with
Command - First parameter must be
context.Context - Remaining parameters are a regular Go parameter list (zero or more typed args)
- Return values can be either just an error, or one return value plus an error
- Streaming commands return a channel instead of a direct value
Adding a New RPC Call
Step 1: Define the Command in the Interface
Add your command to the WshRpcInterface in pkg/wshrpc/wshrpctypes.go:
type WshRpcInterface interface {
// ... existing commands ...
// Add your new command
YourNewCommand(ctx context.Context, data CommandYourNewData) (*YourNewResponse, error)
}
Method Signature Rules:
- Method name must end with
Command - First parameter must be
ctx context.Context - Remaining parameters are a regular Go parameter list (zero or more)
- Return either
erroror(ReturnType, error) - For streaming, return
chan RespOrErrorUnion[T]
Step 2: Define Request and Response Types
If your command needs structured input or output, define types in the same file:
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.
- 8d ago First seen · 454 lines · 36 tokens per session scan A a1a0c314abad
add-rpc is a skill published in the GitHub repository mits-pl/wove (42 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 3,020 once invoked, about $0.0002 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
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
telegram
Owner-only Telegram text bridge and Mini App gateway for the existing Ouroboros interface.
nextjs-fullstack
Use for Next.js App Router, React Server Components, server actions, API routes, auth, database integration, caching, deployment, or full-stack product features.
backend-interview
A simulated technical interview for backend developers, based on the candidate’s resume. It asks foundational questions, explores past projects, and includes one system-design exercise.
api-verification
An API verification workflow that creates both an .http request file and a .cjs JavaScript file, then runs an automation script to test them. An API is an interface through which software exchanges requests and responses.
api-contract-architecture
An architecture guide for public APIs, including HTTP services, software-development kits, command-line tools, schemas, types, errors, pagination, filtering, and compatibility.