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 skills add mpsuesser/pi-effect-harness --skill effect-service-implementationgit 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-service-implementation)<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>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.00017 | $0.04014 |
| Opus 5 | $0.00009 | $0.02007 |
| Sonnet 5 | $0.00003 | $0.00803 |
| Haiku 4.5 | $0.00002 | $0.00401 |
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.
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)
);
}
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.
- 8d ago First seen · 547 lines · 17 tokens per session scan A bc0472eee079
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.
Other skills, from other repositories
effect-patterns-concurrency
Effect-TS patterns for Concurrency. Use when working with concurrency in Effect-TS applications.
effect-patterns-making-http-requests
Effect-TS patterns for Making Http Requests. Use when working with making http requests in Effect-TS applications.
effect-patterns-streams
Effect-TS patterns for Streams. Use when working with streams 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-streams-sinks
Effect-TS patterns for Streams Sinks. Use when working with streams sinks in Effect-TS applications.
effect-patterns-resource-management
Effect-TS patterns for Resource Management. Use when working with resource management in Effect-TS applications.