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/mpsuesser/pi-effect-harness/effect-rpc-apinpx skills add mpsuesser/pi-effect-harness --skill effect-rpc-apigit clone --depth 1 https://github.com/mpsuesser/pi-effect-harnessWrote 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/mpsuesser/pi-effect-harness/effect-rpc-api)<a href="https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-rpc-api"><img src="https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-rpc-api.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.00088 | $0.07560 |
| Opus 5 | $0.00044 | $0.03780 |
| Sonnet 5 | $0.00018 | $0.01512 |
| Haiku 4.5 | $0.00009 | $0.00756 |
Grade A, and why
effect-rpc-api 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 6d 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 — 624 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Effect TypeScript expert specializing in defining shared RPC contracts with Rpc, RpcGroup, RpcSchema, and RpcMiddleware from effect/unstable/rpc.
This skill covers the contract layer: the definitions that client and server packages both import. Wiring handlers into a server is the effect-rpc-server skill; constructing clients and protocols is the effect-rpc-client skill; distributed entities are the effect-rpc-cluster skill.
Effect Source Reference
The Effect v4 source is at ~/.cache/effect-v4/. Read it directly when in doubt — these modules are under unstable and move between betas.
Key files:
packages/effect/src/unstable/rpc/Rpc.ts—Rpc.make,Rpc.custom, per-rpc combinators,exitSchema,Wrapper(fork/uninterruptible/wrap),ServerClient, every type helper (Payload,Success,Error,Exit,ToHandlerFn,ResultFrom, ...)packages/effect/src/unstable/rpc/RpcGroup.ts— group construction and composition (add/merge/omit/prefix/middleware), group vs per-rpc annotations, handler-conversion surface (toLayer/toHandlers/toLayerHandler/accessHandler/of)packages/effect/src/unstable/rpc/RpcSchema.ts— theStreamschema marker,isStreamSchema,ClientAbortcause annotationpackages/effect/src/unstable/rpc/RpcMiddleware.ts—Serviceconstructor,layerClient,ForClient,ApplyServicesand the middleware function shapespackages/effect/src/unstable/rpc/RpcMessage.ts— wire envelopes:Request,Ack,Interrupt,Eof,Ping,ResponseChunk,ResponseExit,ExitEncoded,RequestIdpackages/effect/src/unstable/rpc/RpcClientError.ts— the transport error type referenced when typing shared client aliasespackages/effect/src/unstable/rpc/index.ts— public exports of the rpc namespacepackages/platform-node/test/fixtures/rpc-schemas.ts— the best real-world contract fixture: rpcs, streaming, middleware, deferred responsespackages/effect/test/rpc/Rpc.test.ts—exitSchema, custom defect schemas,getStreamSchemassemantics
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.
- 6d ago First seen · 624 lines · 88 tokens per session scan A 2c8f875c7e24
effect-rpc-api is a skill published in the GitHub repository mpsuesser/pi-effect-harness (24 stars, last pushed 2mo ago), licensed MIT. It adds 88 tokens to every session and 7,560 once invoked, about $0.0004 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
effect-patterns-building-apis
Effect-TS patterns for Building Apis. Use when working with building apis in Effect-TS applications.
effect-patterns-concurrency
Effect-TS patterns for Concurrency. Use when working with concurrency in Effect-TS applications.
effect-patterns-building-data-pipelines
Effect-TS patterns for Building Data Pipelines. Use when working with building data pipelines in Effect-TS applications.
effect-patterns-error-management
Effect-TS patterns for Error Management. Use when working with error management in Effect-TS applications.
effect-patterns-observability
Effect-TS patterns for Observability. Use when working with observability in Effect-TS applications.
effect-patterns-streams
Effect-TS patterns for Streams. Use when working with streams in Effect-TS applications.