relay: Skill for Claude Code

.skills/effect-use-pattern/SKILL.md

effect-client-wrapper is a skill for Claude Code, Codex from adarshp14/relay. It costs 58 tokens per session (1,353 once invoked), scanned A, a copy of effect-client-wrapper, MIT.

A pattern for connecting Effect programs to third-party services such as Stripe, Resend, or AWS. Effect is a TypeScript library for managing errors, configuration, and dependencies in a structured way.

In plain words
What is it for?
Use it when building an Effect service around a third-party SDK with API-key configuration and asynchronous client methods.
Why use it?
It gives external service calls consistent typed errors, tracing, configuration handling, and dependency injection instead of scattered Promise handling.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is adarshp14/relay's own configuration. It tells Claude Code and Codex how to work on relay itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything relay configures →

Reuse

Borrowing it

Nothing to install: this file belongs to adarshp14/relay. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/adarshp14/relay/main/.skills/effect-use-pattern/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/adarshp14/relay

Made for: Claude Code, Codex.

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 effect-client-wrapper

README.md
[![agentmods](https://agentmods.dev/badge/skills/adarshp14/relay/effect-use-pattern/github.svg)](https://agentmods.dev/skills/adarshp14/relay/effect-use-pattern)
Your own site
<a href="https://agentmods.dev/skills/adarshp14/relay/effect-use-pattern"><img src="https://agentmods.dev/badge/skills/adarshp14/relay/effect-use-pattern/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 effect-client-wrapper

Your own site · 80×15
<a href="https://agentmods.dev/skills/adarshp14/relay/effect-use-pattern"><img src="https://agentmods.dev/badge/skills/adarshp14/relay/effect-use-pattern.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,353 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00058 $0.01353
Opus 5.5 $0.00023 $0.00541
Sonnet 5.5 $0.00012 $0.00271
Haiku 4.5 $0.00006 $0.00135

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

Security

Grade A, and why

effect-client-wrapper 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.

Origin

This is a copy

100% identical to effect-client-wrapper — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.skills/effect-use-pattern/SKILL.md · 185 lines

How it starts

The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Effect Client Wrapper Pattern

Wrap third-party SDK clients with Effect using the "use" pattern for consistent error handling, tracing, and dependency injection.

Pattern Structure

import { Context, Data, Effect, Layer, Config, Redacted } from "effect";

// 1. Define tagged errors
export class MyClientError extends Data.TaggedError("MyClientError")<{
  cause: unknown;
}> {}

export class MyClientInstantiationError extends Data.TaggedError("MyClientInstantiationError")<{
  cause: unknown;
}> {}

// 2. Define service interface with `use` method
export type IMyClient = Readonly<{
  client: ThirdPartyClient;
  use: <A>(fn: (client: ThirdPartyClient) => Promise<A>) => Effect.Effect<A, MyClientError, never>;
}>;

// 3. Create the service implementation
const make = Effect.gen(function* () {
  const apiKey = yield* Config.redacted("MY_CLIENT_API_KEY");

  const client = yield* Effect.try({
    try: () => new ThirdPartyClient(Redacted.value(apiKey)),
    catch: (cause) => new MyClientInstantiationError({ cause }),
  });

  const use = <A>(fn: (client: ThirdPartyClient) => Promise<A>) =>
    Effect.tryPromise({
      try: () => fn(client),
      catch: (cause) => new MyClientError({ cause }),
    }).pipe(Effect.withSpan(`my_client.${fn.name ?? "use"}`));

  return { client, use };
});

// 4. Export as Context.Tag with Default layer
export class MyClient extends Context.Tag("MyClient")<MyClient, IMyClient>() {
  static Default = Layer.effect(this, make).pipe(Layer.annotateSpans({ module: "MyClient" }));
}

Usage

const program = Effect.gen(function* () {
  const myClient = yield* MyClient;

  const result = yield* myClient.use((client) => client.someMethod({ param: "value" }));

  return result;
});

// Run with layer
program.pipe(Effect.provide(MyClient.Default));

Key Benefits

  1. Centralized error handling - All client errors wrapped in typed MyClientError
  2. Automatic tracing - Every use call creates a span with function name
  3. Config-based secrets - API keys loaded via Config.redacted
  4. Clean DI - Consumers inject via yield* MyClient
  5. Encapsulation - Raw client hidden behind use interface

Read the full file on GitHub · 185 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 · 185 lines · 58 tokens per session scan A d48e6d0f36e2

Subscribe to this mod's changes

effect-client-wrapper is a skill published in the GitHub repository adarshp14/relay (0 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 1,353 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to effect-client-wrapper, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

webiny-api-cms-custom-field-type

How to implement a custom CMS field type that integrates with the model builder's fluent API. Covers extending DataFieldBuilder, composing validator interfaces, creating a FieldTypeFactory, registering via DI, and module augmentation for TypeScript autocomplete on the fields() registry.

webiny/webiny-js · 60 tokens

nodejs-sdk

Type-safe Node.js API client SDK with validation, mocking, retry, and logging. Use when building API clients for Node.js applications.

pontjs/pontx · 31 tokens

graphql-api-development

Comprehensive guide for building GraphQL APIs including schema design, queries, mutations, subscriptions, resolvers, type system, error handling, authentication, authorization, caching strategies, and production best practices.

manutej/luxor-claude-marketplace · 42 tokens

node

Provides domain-specific best practices for Node.js development with TypeScript, covering type stripping, async patterns, error handling, streams, modules, testing, performance, caching, logging, and more. Use when setting up Node.js projects with native TypeScript support, configuring type stripping…

ushibo/brigade · 162 tokens

fastify-best-practices

Guides development of Fastify Node.js backend servers and REST APIs using TypeScript or JavaScript. Use when building, configuring, or debugging a Fastify application — including defining routes, implementing plugins, setting up JSON Schema validation, handling errors, optimising performance, managing authentication…

ushibo/brigade · 137 tokens

fastapi

FastAPI best practices and conventions. Use when working with FastAPI APIs, Pydantic models, dependencies, streaming responses including Server-Sent Events (SSE), and serving frontend apps. Keeps FastAPI code clean and up to date with the latest features and patterns.

fastapi/fastapi · 57 tokens