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-socketnpx skills add mpsuesser/pi-effect-harness --skill effect-socketgit 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-socket)<a href="https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-socket"><img src="https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-socket.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 | $0.00098 | $0.08407 |
| Opus 5 | $0.00049 | $0.04203 |
| Sonnet 5 | $0.00020 | $0.01681 |
| Haiku 4.5 | $0.00010 | $0.00841 |
Grade A, and why
effect-socket 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 4d 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 — 691 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 bidirectional socket programming with effect/unstable/socket and the Node/Bun platform socket adapters.
These modules live under effect/unstable/socket — there is no @effect/platform/Socket in v4. Platform implementations ship from @effect/platform-node (NodeSocket, NodeSocketServer) and @effect/platform-bun (BunSocket, BunSocketServer), both re-exporting the same shared implementation from @effect/platform-node-shared.
Effect Source Reference
The Effect v4 source is at ~/.cache/effect-v4/. Read it directly when in doubt — these unstable modules change between betas.
Key files:
packages/effect/src/unstable/socket/Socket.ts—Socketinterface and service tag,make,CloseEvent, theSocketErrortaxonomy, channel adapters (toChannel,toChannelString,toChannelMap,makeChannel), WebSocket constructors (makeWebSocket,fromWebSocket,layerWebSocket,WebSocketConstructor),fromTransformStreampackages/effect/src/unstable/socket/SocketServer.ts—SocketServerservice contract,Address(TcpAddress/UnixAddress),SocketServerErrorpackages/platform-node-shared/src/NodeSocket.ts—makeNet,fromDuplex,makeNetChannel,layerNet,NetSocketservice,NodeWS(wsre-export)packages/platform-node-shared/src/NodeSocketServer.ts— TCP/Unix servermake/layer, WebSocket servermakeWebSocket/layerWebSocket,IncomingMessageservicepackages/platform-node/src/NodeSocket.ts— re-exports shared module; addslayerWebSocketConstructor,layerWebSocketConstructorWS,layerWebSocketpackages/platform-bun/src/BunSocket.ts— same shared re-export; Bun-global WebSocket constructor layerspackages/platform-node/test/NodeSocket.test.ts— loopback echo server, WebSocket client semantics, transform-stream socketspackages/effect/src/unstable/devtools/DevToolsClient.ts— production example of NDJSON-framed request/response over aSocketpackages/effect/src/unstable/rpc/RpcClient.ts(makeProtocolSocket) — production example of socket reconnect with retry schedules
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.
- 4d ago First seen · 691 lines · 98 tokens per session scan A 76ac23eb0ffc
effect-socket is a skill published in the GitHub repository mpsuesser/pi-effect-harness (23 stars, last pushed 2mo ago), licensed MIT. It adds 98 tokens to every session and 8,407 once invoked, about $0.0005 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
codebase-memory
Use the codebase knowledge graph for structural code queries. Triggers on: explore the codebase, understand the architecture, what functions exist, show me the structure, who calls this function, what does X call, trace the call chain, find callers of, show dependencies, impact analysis, dead code, unused functions…
using-pi-subagents
Operate pi-subagents jobs safely, including direct-work decisions, least-privilege tool selection, thinking-level selection, delegation, bidirectional messaging, parallel starts, timeout selection, waiting, cancellation, result handling, verification, and writer isolation.
ts-sdk-author
Design, build, verify, and publish production-grade TypeScript SDKs as npm packages inside a pnpm monorepo. Covers workspace layout, public API and module boundaries, plugin extension points, branded types and library-tuned tsconfig, tsdown bundling (vs tsup/tsc-only/unbuild), package.json exports with dual ESM+CJS…
effect
Opinionated guide for building production TypeScript applications with Effect v4. Use when implementing Effect workflows, services, layers, schemas, configuration, schedules, caches, streams, HTTP clients, or tests.
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.