relay: Skill for Claude Code

.skills/effect-http-testing/SKILL.md

effect-http-testing is a skill for Claude Code, Codex from adarshp14/relay. It costs 64 tokens per session (1,632 once invoked), scanned A, a copy of effect-http-testing, MIT.

A testing pattern for Effect HTTP services, including APIs, request handlers, clients, and servers. Tests run against an in-process server rather than requiring a separately deployed service.

In plain words
What is it for?
Use it when testing an HttpApi, HttpApiBuilder handler, HttpClient integration, HttpServer, or another HTTP service built with Effect.
Why use it?
It shows how to compose the required layers and inject an HTTP client, avoiding unreliable tests caused by missing server or dependency setup.

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-http-testing/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-http-testing

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/adarshp14/relay/effect-http-testing"><img src="https://agentmods.dev/badge/skills/adarshp14/relay/effect-http-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,632 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.00064 $0.01632
Opus 5.5 $0.00026 $0.00653
Sonnet 5.5 $0.00013 $0.00326
Haiku 4.5 $0.00006 $0.00163

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

Security

Grade A, and why

effect-http-testing 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-http-testing — 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-http-testing/SKILL.md · 205 lines

How it starts

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

Effect HTTP Testing

Core Pattern

Define an API with HttpApi, implement handlers with HttpApiBuilder.group, serve it with HttpApiBuilder.serve(), and use NodeHttpServer.layerTest to get an in-process test server + HttpClient pointed at it.

import { expect, layer } from "@effect/vitest";
import { Effect, Layer, Schema } from "effect";
import {
  HttpApi,
  HttpApiBuilder,
  HttpApiEndpoint,
  HttpApiGroup,
  HttpClient,
  OpenApi,
} from "@effect/platform";
import { NodeHttpServer } from "@effect/platform-node";

// 1. Define the API
class Item extends Schema.Class<Item>("Item")({
  id: Schema.Number,
  name: Schema.String,
}) {}

const ItemsGroup = HttpApiGroup.make("items")
  .add(HttpApiEndpoint.get("listItems", "/items").addSuccess(Schema.Array(Item)))
  .add(
    HttpApiEndpoint.get("getItem", "/items/:itemId")
      .setPath(Schema.Struct({ itemId: Schema.NumberFromString }))
      .addSuccess(Item),
  );

const MyApi = HttpApi.make("myApi").add(ItemsGroup);

// 2. Implement handlers
const ItemsLive = HttpApiBuilder.group(MyApi, "items", (handlers) =>
  handlers
    .handle("listItems", () => Effect.succeed([{ id: 1, name: "Widget" }]))
    .handle("getItem", (req) => Effect.succeed({ id: req.path.itemId, name: "Widget" })),
);

// 3. Build test layer
const ApiLive = HttpApiBuilder.api(MyApi).pipe(Layer.provide(ItemsLive));

const TestLayer = HttpApiBuilder.serve().pipe(
  Layer.provide(ApiLive),
  Layer.provideMerge(NodeHttpServer.layerTest),
);

// 4. Use layer() to share across tests
layer(TestLayer)("My API", (it) => {
  it.effect("works", () =>
    Effect.gen(function* () {
      const client = yield* HttpClient.HttpClient;
      // client is already pointed at the test server
      const response = yield* client.get("/items");
      // ...
    }),
  );
});

Critical Rules

Layer composition order matters

HttpApiBuilder.serve() consumes HttpApi.Api. The API layer must be provided to it, not the other way around:

// CORRECT
HttpApiBuilder.serve().pipe(Layer.provide(ApiLive), Layer.provideMerge(NodeHttpServer.layerTest));

// WRONG — "Service not found: HttpApi.Api"
ApiLive.pipe(Layer.provide(HttpApiBuilder.serve()), Layer.provideMerge(NodeHttpServer.layerTest));

Read the full file on GitHub · 205 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 · 205 lines · 64 tokens per session scan A a0ab31024509

Subscribe to this mod's changes

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

Related

Other skills, from other repositories

ios-app-tester

Test iOS apps using AXe CLI for accessibility auditing, UI automation, and simulator control. Use when testing iOS Simulator apps, automating UI interactions, recording test videos, or auditing accessibility labels and VoiceOver support.

ckorhonen/claude-skills · 50 tokens

playwright-browser

Use when automating browsers, testing pages, taking screenshots, checking UI, verifying login flows, or testing responsive behavior.

TechNickAI/ai-coding-config · 27 tokens

verification

Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.

build-with-dhiraj/ai-workflow-framework-portability-kit · 46 tokens

agent-browser-verify

Automated browser verification for dev servers. Triggers when a dev server starts to run a visual gut-check with agent-browser — verifies the page loads, checks for console errors, validates key UI elements, and reports pass/fail before continuing.

build-with-dhiraj/ai-workflow-framework-portability-kit · 53 tokens

flutter-testing-apps

Implement unit, widget, and integration tests for a Flutter app. Use for code quality and regression prevention.

build-with-dhiraj/ai-workflow-framework-portability-kit · 26 tokens

benchmark-e2e

End-to-end benchmark suite for vercel-plugin. Runs realistic projects through skill injection, launches dev servers, verifies everything works, analyzes conversation logs, and produces an improvement report for overnight self-improvement loops.

build-with-dhiraj/ai-workflow-framework-portability-kit · 46 tokens