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-project-setup-executionnpx skills add PaulJPhilp/EffectPatterns --skill effect-patterns-project-setup-executiongit 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.00033 | $0.01465 |
| Opus 5 | $0.00016 | $0.00732 |
| Sonnet 5 | $0.00007 | $0.00293 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
effect-patterns-project-setup--execution 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 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.
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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Effect-TS Patterns: Project Setup Execution
This skill provides 4 curated Effect-TS patterns for project setup execution. Use this skill when working on tasks related to:
- project setup execution
- Best practices in Effect-TS applications
- Real-world patterns and solutions
🟢 Beginner Patterns
Execute Synchronous Effects with Effect.runSync
Rule: Execute synchronous effects with Effect.runSync.
Good Example:
import { Effect } from "effect";
// Simple synchronous program
const program1 = Effect.gen(function* () {
const n = 10;
const result = n * 2;
yield* Effect.log(`Simple program result: ${result}`);
return result;
});
// Run simple program
Effect.runSync(program1);
// Program with logging
const program2 = Effect.gen(function* () {
yield* Effect.logInfo("Starting calculation...");
const n = yield* Effect.sync(() => 10);
yield* Effect.logInfo(`Got number: ${n}`);
const result = yield* Effect.sync(() => n * 2);
yield* Effect.logInfo(`Result: ${result}`);
return result;
});
// Run with logging
Effect.runSync(program2);
// Program with error handling
const program3 = Effect.gen(function* () {
yield* Effect.logInfo("Starting division...");
const n = yield* Effect.sync(() => 10);
const divisor = yield* Effect.sync(() => 0);
yield* Effect.logInfo(`Attempting to divide ${n} by ${divisor}...`);
return yield* Effect.try({
try: () => {
if (divisor === 0) throw new Error("Cannot divide by zero");
return n / divisor;
},
catch: (error) => {
if (error instanceof Error) {
return error;
}
return new Error("Unknown error occurred");
},
});
}).pipe(
Effect.catchAll((error) => Effect.logInfo(`Error occurred: ${error.message}`))
);
// Run with error handling
Effect.runSync(program3);
Explanation:
Use runSync only for Effects that are fully synchronous. If the Effect
contains async code, use runPromise instead.
Anti-Pattern:
Do not use runSync on an Effect that contains asynchronous operations like
Effect.delay or Effect.promise. This will result in a runtime error.
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 · 234 lines · 33 tokens per session scan A bdc2a42ea335
effect-patterns-project-setup--execution is a skill published in the GitHub repository PaulJPhilp/EffectPatterns (795 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 1,465 once invoked, about $0.0002 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
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…