build-a-basic-http-server

build-a-basic-http-server is a cursor rule for Cursor from PaulJPhilp/EffectPatterns. It costs 537 tokens per session, scanned A, original, MIT.

A coding rule for building a basic Node.js HTTP server with Effect, a TypeScript library for describing and managing program operations.

In plain words
What is it for?
Creating a small HTTP server that runs an Effect application, logs incoming requests, and returns HTTP responses.
Why use it?
It gives agents a consistent pattern for starting the server and managing the services used to handle requests.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Creating a small HTTP server that runs an Effect application, logs incoming requests, and returns HTTP responses.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/pauljphilp/effectpatterns/build-a-basic-http-server
Install

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.

Clone the repo
git clone --depth 1 https://github.com/PaulJPhilp/EffectPatterns

Made for: Cursor.

Wrote 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.

agentmods badge for build-a-basic-http-server

README.md
[![agentmods](https://agentmods.dev/badge/rules/pauljphilp/effectpatterns/build-a-basic-http-server/github.svg)](https://agentmods.dev/rules/pauljphilp/effectpatterns/build-a-basic-http-server)
Your own site
<a href="https://agentmods.dev/rules/pauljphilp/effectpatterns/build-a-basic-http-server"><img src="https://agentmods.dev/badge/rules/pauljphilp/effectpatterns/build-a-basic-http-server/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.

agentmods 80×15 button for build-a-basic-http-server

Your own site · 80×15
<a href="https://agentmods.dev/rules/pauljphilp/effectpatterns/build-a-basic-http-server"><img src="https://agentmods.dev/badge/rules/pauljphilp/effectpatterns/build-a-basic-http-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 537 This file is loaded in full into every session.
When invoked 537 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00537 $0.00537
Opus 5.5 $0.00215 $0.00215
Sonnet 5.5 $0.00107 $0.00107
Haiku 4.5 $0.00054 $0.00054

Measured 1mo ago against content hash fbf4b7faa903, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

content/published/rules/cursor/build-a-basic-http-server.mdc · 52 lines

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.

  1. Setup Phase: You define all your application's dependencies (database connections, clients, config) in Layers and compose them into a single AppLayer.
  2. Runtime Creation: You use Layer.toRuntime(AppLayer) to create a highly-optimized Runtime object. This is done once when the server starts.
  3. Request Handling: For each incoming request, you create an Effect that describes the work to be done (e.g., parse request, call services, create response).
  4. Execution: You use the Runtime you created in the setup phase to execute the request-handling Effect using Runtime.runPromise.

Read the full file on GitHub · 52 lines

Changes

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.

  1. 1mo ago First seen · 52 lines · 537 tokens per session scan A fbf4b7faa903

Subscribe to this mod's changes

build-a-basic-http-server is a cursor rule published in the GitHub repository PaulJPhilp/EffectPatterns (807 stars, last pushed 4mo ago), licensed MIT. It adds 537 tokens to every session, about $0.0021 per session on Opus 5.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.