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-layer-designgit 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-layer-design)<a href="https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-layer-design"><img src="https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-layer-design.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.00013 | $0.04008 |
| Opus 5 | $0.00006 | $0.02004 |
| Sonnet 5 | $0.00003 | $0.00802 |
| Haiku 4.5 | $0.00001 | $0.00401 |
Grade A, and why
effect-layer-design 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.
How it starts
The opening of the file, as written. The whole thing — 605 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Layer Design Skill
Create layers that construct services while managing their dependencies cleanly.
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:
- Layer source:
packages/effect/src/Layer.ts - Context source:
packages/effect/src/Context.ts - Migration guide:
MIGRATION.md - Effect source:
packages/effect/src/
Layer Structure
import { Layer } from 'effect';
// Layer<RequirementsOut, Error, RequirementsIn>
// ▲ ▲ ▲
// │ │ └─ What this layer needs
// │ └─ Errors during construction
// └─ What this layer produces
Pattern: Simple Layer (No Dependencies)
import { Context, Effect, Layer } from 'effect';
interface ConfigData {
readonly logLevel: string;
readonly connection: string;
}
export class Config extends Context.Service<
Config,
{
readonly getConfig: Effect.Effect<ConfigData>;
}
>()('Config') {}
// Layer<Config, never, never>
// ▲ ▲ ▲
// │ │ └─ No dependencies
// │ └─ Cannot fail
// └─ Produces Config
export const ConfigLive = Layer.succeed(
Config,
Config.of({
getConfig: Effect.succeed({
logLevel: 'INFO',
connection: 'mysql://localhost/db'
})
})
);
Pattern: Layer with Dependencies
import { Context, Effect, Layer, Console } from 'effect';
interface ConfigData {
readonly logLevel: string;
readonly connection: string;
}
export class Config extends Context.Service<
Config,
{
readonly getConfig: Effect.Effect<ConfigData>;
}
>()('Config') {}
export class Logger extends Context.Service<
Logger,
{
readonly log: (message: string) => Effect.Effect<void>;
}
>()('Logger') {}
// Layer<Logger, never, Config>
// ▲ ▲ ▲
// │ │ └─ Needs Config
// │ └─ Cannot fail
// └─ Produces Logger
export const LoggerLive = Layer.effect(
Logger,
Effect.gen(function* () {
const config = yield* Config; // Access dependency
return Logger.of({
log: (message) =>
Effect.gen(function* () {
const { logLevel } = yield* config.getConfig;
yield* Console.log(`[${logLevel}] ${message}`);
})
});
})
);
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.
- 7d ago First seen · 605 lines · 13 tokens per session scan A 5db61c304df4
effect-layer-design is a skill published in the GitHub repository mpsuesser/pi-effect-harness (24 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 4,008 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-building-apis
Effect-TS patterns for Building Apis. Use when working with building apis in Effect-TS applications.
effect-patterns-building-data-pipelines
Effect-TS patterns for Building Data Pipelines. Use when working with building data pipelines 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-domain-modeling
Effect-TS patterns for Domain Modeling. Use when working with domain modeling 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.