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/mpsuesser/pi-effect-harness/effect-schema-compositionnpx skills add mpsuesser/pi-effect-harness --skill effect-schema-compositiongit clone --depth 1 https://github.com/mpsuesser/pi-effect-harnessWrote 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.
[](https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-schema-composition)<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>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.
| Model | Per session | Once 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 |
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.
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
Encoded→Type(e.g., string "123" → number 123) - Encoding: Transform
Type→Encoded(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)
);
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.
- 6d ago First seen · 931 lines · 49 tokens per session scan A ecb8b551a878
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.
Other skills, from other repositories
effect-patterns-concurrency
Effect-TS patterns for Concurrency. Use when working with concurrency in Effect-TS applications.
effect-patterns-streams
Effect-TS patterns for Streams. Use when working with streams in Effect-TS applications.
effect-patterns-streams-sinks
Effect-TS patterns for Streams Sinks. Use when working with streams sinks in Effect-TS applications.
effect-patterns-error-handling
Effect-TS patterns for Error Handling. Use when working with error handling in Effect-TS applications.
effect-patterns-resource-management
Effect-TS patterns for Resource Management. Use when working with resource management in Effect-TS applications.
effect-patterns-scheduling-periodic-tasks
Effect-TS patterns for Scheduling Periodic Tasks. Use when working with scheduling periodic tasks in Effect-TS applications.