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-http-apinpx skills add mpsuesser/pi-effect-harness --skill effect-http-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-http-api)<a href="https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-http-api"><img src="https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-http-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 | $0.00053 | $0.14123 |
| Opus 5 | $0.00026 | $0.07061 |
| Sonnet 5 | $0.00011 | $0.02825 |
| Haiku 4.5 | $0.00005 | $0.01412 |
Grade A, and why
effect-http-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 3d 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,705 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 the HttpApi module for building schema-first HTTP APIs.
Effect Source Reference
The Effect v4 source is available at ~/.cache/effect-v4/. Browse and read files there directly to look up APIs, types, and implementations.
Key reference files:
packages/effect/HTTPAPI.md— canonical HttpApi documentationpackages/effect/src/unstable/httpapi/*.ts— module sourcespackages/effect/typetest/unstable/httpapi/*.tst.ts— type-level contractspackages/platform-node/test/HttpApi.test.ts— comprehensive runtime testsai-docs/src/51_http-server/— server walkthrough with fixturesai-docs/src/50_http-client/— HttpClient walkthrough
Core Imports
// HttpApi modules (definition + building + client + testing)
import {
HttpApi,
HttpApiBuilder,
HttpApiClient,
HttpApiEndpoint,
HttpApiError,
HttpApiGroup,
HttpApiMiddleware,
HttpApiScalar,
HttpApiSchema,
HttpApiSecurity,
HttpApiSwagger,
HttpApiTest,
OpenApi
} from 'effect/unstable/httpapi';
// HTTP primitives (router, server, client, multipart)
import {
FetchHttpClient,
HttpClient,
HttpClientRequest,
HttpClientResponse,
HttpEffect,
HttpRouter,
HttpServer,
HttpServerRequest,
HttpServerResponse,
Multipart
} from 'effect/unstable/http';
// Platform server (Node.js — Bun has @effect/platform-bun/BunHttpServer)
import { NodeHttpServer, NodeRuntime } from '@effect/platform-node';
Architecture Overview
An API is built from three building blocks:
HttpApi
├── HttpApiGroup
│ ├── HttpApiEndpoint
│ └── HttpApiEndpoint
└── HttpApiGroup
├── HttpApiEndpoint
└── HttpApiEndpoint
One definition powers the server, docs, and client — change it once and everything stays in sync.
Critical design rule: API definitions live in their own module/package, separate from server implementations, so clients can import them without pulling in server code or handler dependencies.
Defining Endpoints
HTTP Methods
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.
- 3d ago First seen · 1,705 lines · 53 tokens per session scan A 1cf2b7e5b70b
effect-http-api is a skill published in the GitHub repository mpsuesser/pi-effect-harness (23 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 14,123 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
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.
code-design
TypeScript conventions, code design principles (SOLID, self-documenting code, file organization), structural design heuristics (dependency width, LoD, output arguments), pnpm rules, ES2024 target, Pi SDK patterns, and Biome/ESLint conflict workarounds. Load during implementation, refactoring, or code review.
pi
Use when needing a minimal, extensible terminal AI coding agent harness in TypeScript with plugin architecture. Pi: minimalist terminal AI coding agent emphasizing simplicity and composability.
typescript-style
Validate TypeScript/React code against style and architectural conventions.
effect-best-practices
Enforces Effect-TS patterns for services, errors, layers, and atoms. Use when writing code with Effect.Service, Schema.TaggedError, Layer composition, or effect-atom React components.