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-atom-rpcWrote 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-atom-rpc)<a href="https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-atom-rpc"><img src="https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-atom-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.00048 | $0.04904 |
| Opus 5 | $0.00024 | $0.02452 |
| Sonnet 5 | $0.00010 | $0.00981 |
| Haiku 4.5 | $0.00005 | $0.00490 |
Grade A, and why
effect-atom-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 — 487 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/reactivity/AtomRpc — the reactive RPC client for Atom-driven frontends.
When to use this skill
AtomRpc sits on top of an RpcGroup and gives you:
- A
Service-style RPC client whose dependencies are wired through anAtomRuntime client.query(tag, payload, options?)— a cached, reactiveAtom<AsyncResult<...>>client.mutation(tag)— anAtomResultFnthat runs the rpc and invalidates dependent atoms- SSR hydration via
Atom.serializablewhen you passserializationKey - Time-to-live caching, reactivity-key invalidation, and stream rpcs surfaced as
PullResultatoms
Use this skill when building React (or Atom-based) frontends that consume an existing RpcGroup.
For the underlying RPC definitions, see the effect-rpc-cluster skill.
For Atom fundamentals (Atom.make, family, keepAlive, AsyncResult, hydration), see the effect-atom-state and effect-react-vm skills.
Effect Source Reference
packages/effect/src/unstable/reactivity/AtomRpc.ts— the whole API (~270 lines)packages/effect/test/reactivity/AtomRpc.test.ts— minimal usage + serialization testpackages/effect/src/unstable/reactivity/AtomHttpApi.ts— the cousin pattern forHttpApi(same idea, same options)packages/effect/src/unstable/reactivity/AsyncResult.ts— theAsyncResulttype returned byquerypackages/effect/src/unstable/reactivity/Atom.ts—runtime,family,serializable,keepAlive,setIdleTTLpackages/effect/src/unstable/reactivity/Hydration.ts— SSR dehydrate/hydrate helperspackages/effect/src/unstable/reactivity/Reactivity.ts— theReactivityservice that powers reactivity keys
Imports
import {
AsyncResult,
Atom,
AtomRpc,
Hydration,
Reactivity
} from 'effect/unstable/reactivity';
import { RpcClient, RpcSerialization } from 'effect/unstable/rpc';
import { FetchHttpClient } from 'effect/unstable/http';
import { useAtomValue, useAtomSet } from '@effect/atom-react';
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 · 487 lines · 48 tokens per session scan A af04606ba23c
effect-atom-rpc is a skill published in the GitHub repository mpsuesser/pi-effect-harness (24 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 4,904 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
algolia-search-v2
Algolia Search Integration workflow skill. Use this skill when the user needs Expert patterns for Algolia search implementation, indexing and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
algolia-search-v3
Algolia Search Integration workflow skill. Use this skill when the user needs Expert patterns for Algolia search implementation, indexing and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
algolia-search-v4
Algolia Search Integration workflow skill. Use this skill when the user needs Expert patterns for Algolia search implementation, indexing and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
nextjs-app-router
Full end-to-end tRPC setup for Next.js App Router. Covers route handler with fetchRequestHandler (GET + POST exports), TRPCProvider with QueryClientProvider, createTRPCOptionsProxy for RSC prefetching, HydrateClient/HydrationBoundary for hydration, useSuspenseQuery for Suspense, and server-side callers.
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
langbot-dev
Develop, build, and debug the LangBot core backend and web frontend. Use when working inside the LangBot repository — backend (Python/Quart, src/langbot/pkg), the Vite/React web UI, HTTP API controllers/services, Alembic migrations, or the MCP server. Covers the dev environment (uv, pnpm), repo layout, the API auth…