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 mpsuesser/pi-effect-harness --skill effect-rpc-clientgit 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-client)<a href="https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-rpc-client"><img src="https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-rpc-client.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.08916 |
| Opus 5 | $0.00044 | $0.04458 |
| Sonnet 5 | $0.00018 | $0.01783 |
| Haiku 4.5 | $0.00009 | $0.00892 |
Grade A, and why
effect-rpc-client 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 — 660 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 consuming RPC services with RpcClient from effect/unstable/rpc.
This skill covers the client side only: building clients, transports, serialization, headers, streaming consumption, interruption, errors, and testing. Defining Rpc/RpcGroup contracts is the effect-rpc-api skill; serving them is the effect-rpc-server skill; cluster entity clients 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 change between betas.
Key files:
packages/effect/src/unstable/rpc/RpcClient.ts—make,makeNoSerialization, theProtocolservice,layerProtocolHttp/layerProtocolSocket/layerProtocolWorker(+makeProtocol*),CurrentHeaders,withHeaders,ConnectionHookspackages/effect/src/unstable/rpc/RpcClientError.ts—RpcClientErrorandRpcClientDefectpackages/effect/src/unstable/rpc/RpcSerialization.ts—json,ndjson,jsonRpc,ndJsonRpc,msgPackcodecs, their layers, theParserinterface andincludesFramingpackages/effect/src/unstable/rpc/RpcTest.ts—makeClientin-process test clientpackages/effect/src/unstable/rpc/RpcWorker.ts—InitialMessage,layerInitialMessage,initialMessagepackages/effect/src/unstable/rpc/RpcMessage.ts— wire vocabulary:Request,Ack,Interrupt,Chunk,Exit,Defect,Ping/Pong,ClientProtocolError,RequestIdpackages/effect/src/unstable/socket/Socket.ts—Socketservice,layerWebSocket,WebSocketConstructorpackages/platform-node/test/RpcServer.test.ts+test/fixtures/rpc-e2e.ts+test/fixtures/rpc-schemas.ts— the best end-to-end reference: every transport × serialization combination, headers, streams, interrupts, defectspackages/platform-browser/test/RpcWorker.test.ts+test/fixtures/rpc-worker.ts— worker transport end to end
Core Model
A client is assembled from three replaceable layers plus your shared RpcGroup definition:
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 · 660 lines · 88 tokens per session scan A 09e6886587e6
effect-rpc-client 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 8,916 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-building-data-pipelines
Effect-TS patterns for Building Data Pipelines. Use when working with building data pipelines in Effect-TS applications.
effect-patterns-making-http-requests
Effect-TS patterns for Making Http Requests. Use when working with making http requests in Effect-TS applications.
effect-patterns-domain-modeling
Effect-TS patterns for Domain Modeling. Use when working with domain modeling in Effect-TS applications.
effect-patterns-streams-sinks
Effect-TS patterns for Streams Sinks. Use when working with streams sinks in Effect-TS applications.
effect-patterns-resource-management
Effect-TS patterns for Resource Management. Use when working with resource management in Effect-TS applications.