effect-schema-composition

effect-schema-composition is a skill for Claude Code, Codex from mpsuesser/pi-effect-harness. It costs 49 tokens per session (6,100 once invoked), scanned A, original, MIT.

Guidance for combining Effect Schema rules to decode, transform, filter, and validate data in several stages. Effect Schema is a TypeScript tool for describing the shape of data and checking it at runtime.

In plain words
What is it for?
Use it when building or reviewing TypeScript code that combines schemas, converts values such as strings to numbers, applies filters, or validates data through multiple transformations.
Why use it?
It helps keep multi-step data conversion and validation consistent, especially when raw input and final program data have different forms.

Skill for Claude CodeCodex

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

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.

agentmods
npx agentmods add skills/mpsuesser/pi-effect-harness/effect-schema-composition
Any agent
npx skills add mpsuesser/pi-effect-harness --skill effect-schema-composition
Clone the repo
git clone --depth 1 https://github.com/mpsuesser/pi-effect-harness

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-schema-composition

README.md
[![agentmods](https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-schema-composition.svg)](https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-schema-composition)
Your own site
<a href="https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-schema-composition"><img src="https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-schema-composition.svg" alt="Measured on agentmods" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,100 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00049 $0.06100
Opus 5 $0.00024 $0.03050
Sonnet 5 $0.00010 $0.01220
Haiku 4.5 $0.00005 $0.00610

Measured 6d ago against content hash ecb8b551a878, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

effect-schema-composition 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 6d 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.

harnesses/effect/skills/effect-schema-composition/SKILL.md · 931 lines

How it starts

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

Schema Composition Skill

Expert guidance for composing, transforming, and validating data with Effect Schema (v4).

Effect Source Reference

The Effect v4 source is available at ~/.cache/effect-v4/. Browse and read files there directly to look up APIs, types, and implementations.

Reference this for:

  • Full Schema API: packages/effect/SCHEMA.md
  • Schema source: packages/effect/src/Schema.ts
  • SchemaTransformation source: packages/effect/src/SchemaTransformation.ts
  • Migration guide: MIGRATION.md
  • Effect source: packages/effect/src/

Core Concepts

The Schema Type

Every schema in Effect has the type signature Schema<Type, Encoded, Context> where:

  • Type: The validated, decoded output type (what you get after successful decoding)
  • Encoded: The raw input type (what you provide for decoding)
  • Context: External dependencies required for encoding/decoding (often never)

Example:

import { Schema } from 'effect';

// Schema<number, string, never>
//        ^Type  ^Encoded ^Context
const NumberFromString = Schema.NumberFromString;

Decoding vs Encoding

  • Decoding: Transform EncodedType (e.g., string "123" → number 123)
  • Encoding: Transform TypeEncoded (e.g., number 123 → string "123")

Effect Schema follows "parse, don't validate" — schemas transform data into the desired format, not just check validity.

Schema.decodeTo — Chaining Transformations

Use Schema.decodeTo to chain schemas with different types at each stage. It connects the output type of one schema to the input type of another. This replaces the v3 Schema.compose.

When to Use:

  • Multi-step transformations where each stage changes the type
  • Connecting parsing and validation steps
  • Building pipelines from Encoded → Intermediate → Type

Example — Schema composition (no transformation):

import { Schema, SchemaTransformation } from 'effect';

// Convert meters → kilometers → miles via schema composition
const KilometersFromMeters = Schema.Finite.pipe(
	Schema.decode(
		SchemaTransformation.transform({
			decode: (meters) => meters / 1000,
			encode: (kilometers) => kilometers * 1000
		})
	)
);

const MilesFromKilometers = Schema.Finite.pipe(
	Schema.decode(
		SchemaTransformation.transform({
			decode: (kilometers) => kilometers * 0.621371,
			encode: (miles) => miles / 0.621371
		})
	)
);

// Compose the two schemas — no explicit transformation needed
const MilesFromMeters = KilometersFromMeters.pipe(
	Schema.decodeTo(MilesFromKilometers)
);

Read the full file on GitHub · 931 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. 6d ago First seen · 931 lines · 49 tokens per session scan A ecb8b551a878

Subscribe to this mod's changes

effect-schema-composition is a skill published in the GitHub repository mpsuesser/pi-effect-harness (24 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 6,100 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.