Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mpsuesser/pi-effect-harnessnpx agentmods add skills/mpsuesser/pi-effect-harness/effect-rpc-clusterWrote 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-cluster)<a href="https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-rpc-cluster"><img src="https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-rpc-cluster/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-rpc-cluster"><img src="https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-rpc-cluster.svg" alt="Reviewed on agentmods" width="80" 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.00068 | $0.16326 |
| Opus 5 | $0.00034 | $0.08163 |
| Sonnet 5 | $0.00014 | $0.03265 |
| Haiku 4.5 | $0.00007 | $0.01633 |
Grade A, and why
effect-rpc-cluster 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 9d 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 — 1,585 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 effect/unstable/rpc and effect/unstable/cluster.
These modules live under effect/unstable/*. There are no @effect/rpc or @effect/cluster packages in v4 — everything ships from the effect package. APIs may move between betas.
Effect Source Reference
The Effect v4 source is at ~/.cache/effect-v4/. Read it directly when in doubt — the shape of these modules changes more often than the website docs.
Key files:
packages/effect/src/unstable/rpc/Rpc.ts—Rpc.make, custom constructors,Wrapper,ServerClient,exitSchemapackages/effect/src/unstable/rpc/RpcGroup.ts— group construction, handler wiring (toLayer/toHandlers/toLayerHandler/accessHandler), prefixing, omit/merge, annotationspackages/effect/src/unstable/rpc/RpcServer.ts—make,layer,layerHttp, everylayerProtocol*andtoHttpEffect*packages/effect/src/unstable/rpc/RpcClient.ts—make,Protocol, everylayerProtocol*,withHeaders,CurrentHeaders,ConnectionHookspackages/effect/src/unstable/rpc/RpcMiddleware.ts—Serviceconstructor,layerClientpackages/effect/src/unstable/rpc/RpcSerialization.ts— json/ndjson/jsonRpc/ndJsonRpc/msgPack codecs and their layerspackages/effect/src/unstable/rpc/RpcTest.ts— in-process test clientpackages/effect/src/unstable/rpc/RpcWorker.ts—InitialMessagefor worker transportspackages/effect/src/unstable/rpc/RpcSchema.ts—Streamschema marker,ClientAbortcause annotationpackages/effect/src/unstable/rpc/RpcClientError.ts— client-side error unionpackages/effect/src/unstable/cluster/Entity.ts—Entity.make/fromRpcGroup, handler envelopes,Replier,CurrentAddress,keepAlive,makeTestClientpackages/effect/src/unstable/cluster/ClusterSchema.ts—Persisted,Uninterruptible,WithTransaction,ShardGroup,ClientTracingEnabled,Dynamicpackages/effect/src/unstable/cluster/ClusterError.ts—MailboxFull,AlreadyProcessingMessage,PersistenceError,EntityNotAssignedToRunner,MalformedMessage,RunnerUnavailable,RunnerNotRegisteredpackages/effect/src/unstable/cluster/Sharding.ts— theShardingservice surfacepackages/effect/src/unstable/cluster/ShardingConfig.ts— config schema + env loaderpackages/effect/src/unstable/cluster/Singleton.ts— singleton-per-cluster effectspackages/effect/src/unstable/cluster/ClusterCron.ts— cron-driven singletonspackages/effect/src/unstable/cluster/SingleRunner.ts— single-node sql-backed bundlepackages/effect/src/unstable/cluster/TestRunner.ts— in-memory testing bundlepackages/effect/src/unstable/cluster/EntityProxy.ts+EntityProxyServer.ts— entity ↔ RPC/HTTP bridgepackages/effect/src/unstable/workflow/WorkflowProxy.ts+WorkflowProxyServer.ts— workflow ↔ RPC/HTTP bridgepackages/effect/src/unstable/cluster/ClusterWorkflowEngine.ts— production workflow engine backed by sharding + storagepackages/effect/src/unstable/reactivity/AtomRpc.ts— reactive RPC client for Atom UIs (see alsoeffect-atom-rpcskill)packages/platform-node/src/NodeClusterHttp.ts/NodeClusterSocket.ts— Node "all-in-one" cluster layerspackages/platform-bun/src/BunClusterHttp.ts/BunClusterSocket.ts— Bun equivalentspackages/platform-node/test/RpcServer.test.ts+test/fixtures/rpc-{schemas,e2e}.ts— best end-to-end reference for real RPC wiringpackages/effect/test/cluster/TestEntity.ts+test/cluster/Entity.test.ts— best reference for Entity + makeTestClient
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.
- 9d ago First seen · 1,585 lines · 68 tokens per session scan A 751ca3d561da
effect-rpc-cluster is a skill published in the GitHub repository mpsuesser/pi-effect-harness (24 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 16,326 once invoked, about $0.0003 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.