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 rules/pauljphilp/effectpatterns/build-a-basic-http-servergit clone --depth 1 https://github.com/PaulJPhilp/EffectPatternsWhat 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.00537 | $0.00537 |
| Opus 5 | $0.00269 | $0.00269 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
build-a-basic-http-server 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 yesterday.
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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: Use a managed Runtime created from a Layer to handle requests in a Node.js HTTP server. globs: "**/*.ts" alwaysApply: true
Build a Basic HTTP Server
Rule: Use a managed Runtime created from a Layer to handle requests in a Node.js HTTP server.
Example
This example creates a simple server with a Greeter service. The server starts, creates a runtime containing the Greeter, and then uses that runtime to handle requests.
import { HttpServer, HttpServerResponse } from "@effect/platform";
import { NodeHttpServer } from "@effect/platform-node";
import { Duration, Effect, Fiber, Layer } from "effect";
import { createServer } from "node:http";
// Create a server layer using Node's built-in HTTP server
const ServerLive = NodeHttpServer.layer(() => createServer(), { port: 3001 });
// Define your HTTP app (here responding "Hello World" to every request)
const app = Effect.gen(function* () {
yield* Effect.logInfo("Received HTTP request");
return yield* HttpServerResponse.text("Hello World");
});
const serverLayer = HttpServer.serve(app).pipe(Layer.provide(ServerLive));
const program = Effect.gen(function* () {
yield* Effect.logInfo("Server starting on http://localhost:3001");
const fiber = yield* Layer.launch(serverLayer).pipe(Effect.fork);
yield* Effect.sleep(Duration.seconds(2));
yield* Fiber.interrupt(fiber);
yield* Effect.logInfo("Server shutdown complete");
});
Effect.runPromise(program as unknown as Effect.Effect<void, unknown, never>);
Explanation:
This pattern demonstrates the complete lifecycle of a long-running Effect application.
- Setup Phase: You define all your application's dependencies (database connections, clients, config) in
Layers and compose them into a singleAppLayer. - Runtime Creation: You use
Layer.toRuntime(AppLayer)to create a highly-optimizedRuntimeobject. This is done once when the server starts. - Request Handling: For each incoming request, you create an
Effectthat describes the work to be done (e.g., parse request, call services, create response). - Execution: You use the
Runtimeyou created in the setup phase to execute the request-handlingEffectusingRuntime.runPromise.
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.
- yesterday First seen · 52 lines · 537 tokens per session scan A fbf4b7faa903
build-a-basic-http-server is a cursor rule published in the GitHub repository PaulJPhilp/EffectPatterns (794 stars, last pushed 2mo ago), licensed MIT. It adds 537 tokens to every session, about $0.0027 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 cursor rules, from other repositories
transcreveai
Required handoff contract for nested TranscreveAI executions.
cursorrules
You are an expert software engineer and architect. You are part of a team, but your memory is reset after every session. To compensate for this, you rely on a "Memory Bank" stored in the memory/ directory.
typescript-coding-style
Enforces code style and best practices for TypeScript files.
javascript-typescript-code-style
Rules for JavaScript and TypeScript code style, including modern features, functional patterns, and descriptive naming conventions.
astro-development-guidelines
Enforces specific development guidelines for Astro projects, including TypeScript strictness and TailwindCSS usage.
convex-development---general
Applies general rules for Convex development, emphasizing schema design, validator usage, and correct handling of system fields.