effect-incremental-migration

effect-incremental-migration is a skill for Claude Code, Codex from mpsuesser/pi-effect-harness. It costs 52 tokens per session (2,878 once invoked), scanned A, original, MIT.

Instructions for gradually changing asynchronous JavaScript or TypeScript modules to Effect services while keeping older callers working.

In plain words
What is it for?
Use them when converting a module to Effect, defining service interfaces, or maintaining both asynchronous and Effect APIs during the transition.
Why use it?
They provide a structured migration path so new Effect-based code can be introduced without breaking existing Promise-based code.

Skill for Claude CodeCodex

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

Good fit Use them when converting a module to Effect, defining service interfaces, or…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mpsuesser/pi-effect-harness/effect-incremental-migration
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.

Any agent
npx skills add mpsuesser/pi-effect-harness --skill effect-incremental-migration
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-incremental-migration

README.md
[![agentmods](https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-incremental-migration.svg)](https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-incremental-migration)
Your own site
<a href="https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-incremental-migration"><img src="https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-incremental-migration.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,878 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 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.00052 $0.02878
Opus 5 $0.00026 $0.01439
Sonnet 5 $0.00010 $0.00576
Haiku 4.5 $0.00005 $0.00288

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

Security

Grade A, and why

effect-incremental-migration 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 7d 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-incremental-migration/SKILL.md · 363 lines

How it starts

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

Incremental Migration Skill

This skill provides a step-by-step template for converting existing async/Promise-based modules to Effect services. Preserve backward compatibility only where you still have non-Effect callers. The main goal is to move Effect callers onto yield* SomeService.Service early so dependency edges become explicit in the code and in the layer graph.

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:

  • Context source: packages/effect/src/Context.ts
  • Layer source: packages/effect/src/Layer.ts
  • ManagedRuntime source: packages/effect/src/ManagedRuntime.ts
  • Migration guide: MIGRATION.md
  • Effect source: packages/effect/src/

The 7-Step Migration Template

Step 1: Define the Service Interface

Extract a named Interface type with Effect-returning methods. Keep parameter and return types identical to the original module — only swap Promise<T> for Effect.Effect<T, E>.

import type { Effect } from 'effect';

export namespace MyModule {
	export interface Interface {
		readonly get: (id: string) => Effect.Effect<Item, MyModuleError>;
		readonly list: Effect.Effect<ReadonlyArray<Item>>;
	}
}

Step 2: Declare the Service Class

Empty class body — no make:, no static readonly layer. The interface and service class live in the same namespace.

import { Context } from 'effect';
import type { Effect } from 'effect';

export namespace MyModule {
	export interface Interface {
		readonly get: (id: string) => Effect.Effect<Item, MyModuleError>;
		readonly list: Effect.Effect<ReadonlyArray<Item>>;
	}

	export class Service extends Context.Service<Service, Interface>()(
		'@app/MyModule'
	) {}
}

Step 3: Build the Raw Layer

Construct the service inside Layer.effect, capturing dependencies via yield*. Use Effect.fn for traced methods.

import { Effect, Layer, Context } from 'effect';

export namespace MyModule {
	export interface Interface {
		readonly get: (id: string) => Effect.Effect<Item, MyModuleError>;
		readonly list: Effect.Effect<ReadonlyArray<Item>>;
	}

	export class Service extends Context.Service<Service, Interface>()(
		'@app/MyModule'
	) {}

	export const layer = Layer.effect(
		Service,
		Effect.gen(function* () {
			const config = yield* Config.Service;
			const db = yield* Database.Service;

			const get = Effect.fn('MyModule.get')(function* (id: string) {
				const cfg = yield* config.get();
				return yield* db.findById(cfg.table, id);
			});

			const list = Effect.fn('MyModule.list')(function* () {
				const cfg = yield* config.get();
				return yield* db.listAll(cfg.table);
			});

			return Service.of({ get, list });
		})
	);
}

Read the full file on GitHub · 363 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. 7d ago First seen · 363 lines · 52 tokens per session scan A 31b05f537797

Subscribe to this mod's changes

effect-incremental-migration is a skill published in the GitHub repository mpsuesser/pi-effect-harness (24 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 2,878 once invoked, about $0.0003 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.