effect-service-implementation

effect-service-implementation is a skill for Claude Code, Codex from mpsuesser/pi-effect-harness. It costs 17 tokens per session (4,014 once invoked), scanned A, original, MIT.

A guide for building Effect services as small, focused TypeScript capabilities. Effect is a TypeScript library for structuring programs with explicit dependencies, errors, and resource handling.

In plain words
What is it for?
Use it to declare services, create their implementation layers, and combine focused capabilities into larger Effect applications.
Why use it?
It helps avoid one large service that is difficult to understand or change. Dependencies remain visible when services are composed.

Skill for Claude CodeCodex

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

Good fit Use it to declare services, create their implementation layers, and combine focused capabilities into larger Effect applications.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-service-implementation.svg)](https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-service-implementation)
Your own site
<a href="https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-service-implementation"><img src="https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-service-implementation.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,014 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.00017 $0.04014
Opus 5 $0.00009 $0.02007
Sonnet 5 $0.00003 $0.00803
Haiku 4.5 $0.00002 $0.00401

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

Security

Grade A, and why

effect-service-implementation 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 8d 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-service-implementation/SKILL.md · 547 lines

How it starts

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

Service Implementation Skill

Design and implement Effect services as focused capabilities that compose into complete solutions.

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
  • Migration guide: MIGRATION.md
  • Effect source: packages/effect/src/

Service Declaration: Namespace-Module Pattern

The recommended pattern organizes each service as a TypeScript namespace containing: an Interface type, a Service class (pure tag/identifier), and layer / defaultLayer exports. The class body is always empty — construction logic lives in Layer.effect, not in make: or class statics.

The main payoff is a visible service graph. Prefer patterns that make dependencies obvious at yield* call sites and in defaultLayer composition over patterns that keep compatibility shims or helper modules in the foreground.

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

class UserNotFound extends Schema.TaggedErrorClass<UserNotFound>()(
	'UserNotFound',
	{
		userId: Schema.String,
		message: Schema.String
	}
) {}

export namespace UserRepository {
	export interface Interface {
		readonly findById: (id: string) => Effect.Effect<User, UserNotFound>;
		readonly create: (data: CreateUserData) => Effect.Effect<User>;
	}

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

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

			const findById = Effect.fn('UserRepository.findById')(function* (
				id: string
			) {
				const row = yield* db.query(
					'SELECT * FROM users WHERE id = ?',
					id
				);
				if (!row)
					return yield* new UserNotFound({
						userId: id,
						message: `User ${id} not found`
					});
				return row as User;
			});

			const create = Effect.fn('UserRepository.create')(function* (
				data: CreateUserData
			) {
				return yield* db.insert('users', data);
			});

			return Service.of({ findById, create });
		})
	);

	export const defaultLayer = layer.pipe(
		Layer.provide(DatabaseClient.defaultLayer)
	);
}

Read the full file on GitHub · 547 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. 8d ago First seen · 547 lines · 17 tokens per session scan A bc0472eee079

Subscribe to this mod's changes

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