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/pauljphilp/effectpatterns/effect-patterns-making-http-requestsnpx skills add PaulJPhilp/EffectPatterns --skill effect-patterns-making-http-requestsgit 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.00030 | $0.11094 |
| Opus 5 | $0.00015 | $0.05547 |
| Sonnet 5 | $0.00006 | $0.02219 |
| Haiku 4.5 | $0.00003 | $0.01109 |
Grade A, and why
effect-patterns-making-http-requests scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
fetch(url).then((res) => res.json() as T) How it starts
The opening of the file, as written. The whole thing — 1,757 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Effect-TS Patterns: Making Http Requests
This skill provides 10 curated Effect-TS patterns for making http requests. Use this skill when working on tasks related to:
- making http requests
- Best practices in Effect-TS applications
- Real-world patterns and solutions
🟢 Beginner Patterns
Parse JSON Responses Safely
Rule: Always validate HTTP responses with Schema to catch API changes at runtime.
Good Example:
import { Effect, Console } from "effect"
import { Schema } from "effect"
import { HttpClient, HttpClientRequest, HttpClientResponse } from "@effect/platform"
import { NodeHttpClient, NodeRuntime } from "@effect/platform-node"
// ============================================
// 1. Define response schemas
// ============================================
const PostSchema = Schema.Struct({
id: Schema.Number,
title: Schema.String,
body: Schema.String,
userId: Schema.Number,
})
type Post = Schema.Schema.Type<typeof PostSchema>
const PostArraySchema = Schema.Array(PostSchema)
// ============================================
// 2. Fetch and validate single item
// ============================================
const getPost = (id: number) =>
Effect.gen(function* () {
const client = yield* HttpClient.HttpClient
const response = yield* client.get(
`https://jsonplaceholder.typicode.com/posts/${id}`
)
const json = yield* HttpClientResponse.json(response)
// Validate against schema - fails if data doesn't match
const post = yield* Schema.decodeUnknown(PostSchema)(json)
return post
})
// ============================================
// 3. Fetch and validate array
// ============================================
const getPosts = Effect.gen(function* () {
const client = yield* HttpClient.HttpClient
const response = yield* client.get(
"https://jsonplaceholder.typicode.com/posts"
)
const json = yield* HttpClientResponse.json(response)
// Validate array of posts
const posts = yield* Schema.decodeUnknown(PostArraySchema)(json)
return posts
})
// ============================================
// 4. Handle validation errors
// ============================================
const safeGetPost = (id: number) =>
getPost(id).pipe(
Effect.catchTag("ParseError", (error) =>
Effect.gen(function* () {
yield* Console.error(`Invalid response format: ${error.message}`)
// Return a default or fail differently
return yield* Effect.fail(new Error(`Post ${id} has invalid format`))
})
)
)
// ============================================
// 5. Schema with optional fields
// ============================================
const UserSchema = Schema.Struct({
id: Schema.Number,
name: Schema.String,
email: Schema.String,
phone: Schema.optional(Schema.String), // May not exist
website: Schema.optional(Schema.String),
company: Schema.optional(
Schema.Struct({
name: Schema.String,
catchPhrase: Schema.optional(Schema.String),
})
),
})
const getUser = (id: number) =>
Effect.gen(function* () {
const client = yield* HttpClient.HttpClient
const response = yield* client.get(
`https://jsonplaceholder.typicode.com/users/${id}`
)
const json = yield* HttpClientResponse.json(response)
return yield* Schema.decodeUnknown(UserSchema)(json)
})
// ============================================
// 6. Run examples
// ============================================
const program = Effect.gen(function* () {
yield* Console.log("=== Validated Single Post ===")
const post = yield* getPost(1)
yield* Console.log(`Title: ${post.title}`)
yield* Console.log("\n=== Validated Posts Array ===")
const posts = yield* getPosts
yield* Console.log(`Fetched ${posts.length} posts`)
yield* Console.log("\n=== User with Optional Fields ===")
const user = yield* getUser(1)
yield* Console.log(`User: ${user.name}`)
yield* Console.log(`Company: ${user.company?.name ?? "N/A"}`)
})
program.pipe(
Effect.provide(NodeHttpClient.layer),
NodeRuntime.runMain
)
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.
- 2d ago First seen · 1,757 lines · 30 tokens per session scan A 8bc3b6ca6f53
effect-patterns-making-http-requests is a skill published in the GitHub repository PaulJPhilp/EffectPatterns (795 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 11,094 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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.
effect-http-api
Build typed HTTP APIs with Effect's HttpApi — endpoints with schemas, handlers, security middleware, OpenAPI docs, derived clients, and handler unit tests. Use when building HTTP servers, REST APIs, or typed HTTP clients with Effect v4.
effect-error-handling
Implement typed error handling in Effect v4 using Schema.TaggedErrorClass, catchTag/catchTags, catchReason/catchReasons, Cause, ErrorReporter, and recovery patterns. Use this skill when working with Effect error channels, handling expected failures, or designing error recovery strategies.
effect-http-server
Build HTTP servers with effect/unstable/http — HttpRouter routes and middleware, HttpServerRequest schema decoding, HttpServerResponse constructors, multipart uploads, websocket upgrades, static files, NodeHttpServer/BunHttpServer layers, and in-memory web handlers. Use when serving raw HTTP routes, reading request…
effect-fiber
Fork, supervise, and interrupt Effect fibers with Effect.forkChild/forkScoped/forkIn/forkDetach, Fiber join/await/interrupt, uninterruptible regions, and the FiberHandle/FiberMap/FiberSet supervision collections. Use when running background work, cancelling or restarting tasks, implementing latest-wins or keyed…
effect-http-client
Make outgoing HTTP requests with Effect's HttpClient — HttpClientRequest builders, schema-decoded HttpClientResponse bodies, the HttpClientError taxonomy, retryTransient/rate limiting/cookies/redirects, streaming uploads and downloads, and FetchHttpClient/NodeHttpClient transport layers. Use when calling external…