effect-ontology: Skill for Claude Code

.claude/skills/effect-layers-services/SKILL.md

effect-layers-services is a skill for Claude Code from mepuka/effect-ontology. It costs 27 tokens per session (696 once invoked), scanned A, original, MIT.

A guide to organizing Effect services, which are reusable parts of an application, and layers, which connect those services to working implementations. It shows how to switch between live and test versions.

In plain words
What is it for?
Use it to define service interfaces, provide implementations, combine application dependencies, and choose test or live services.
Why use it?
It keeps dependency setup in one place and makes it easier to replace databases, loggers, or other infrastructure during tests.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is mepuka/effect-ontology's own configuration. It tells Claude Code how to work on effect-ontology itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything effect-ontology configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mepuka/effect-ontology. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mepuka/effect-ontology/main/.claude/skills/effect-layers-services/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/mepuka/effect-ontology

Made for: Claude Code.

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-layers-services

README.md
[![agentmods](https://agentmods.dev/badge/skills/mepuka/effect-ontology/effect-layers-services/github.svg)](https://agentmods.dev/skills/mepuka/effect-ontology/effect-layers-services)
Your own site
<a href="https://agentmods.dev/skills/mepuka/effect-ontology/effect-layers-services"><img src="https://agentmods.dev/badge/skills/mepuka/effect-ontology/effect-layers-services/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for effect-layers-services

Your own site · 80×15
<a href="https://agentmods.dev/skills/mepuka/effect-ontology/effect-layers-services"><img src="https://agentmods.dev/badge/skills/mepuka/effect-ontology/effect-layers-services.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 696 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.00027 $0.00696
Opus 5.5 $0.00011 $0.00278
Sonnet 5.5 $0.00005 $0.00139
Haiku 4.5 $0.00003 $0.00070

Measured 2mo ago against content hash e1710922ad9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

effect-layers-services 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 2mo 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.

.claude/skills/effect-layers-services/SKILL.md · 93 lines

How it starts

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

Layers & Services

When to use

  • You need DI boundaries or swapping test/live implementations
  • You want to compose infra (logger, db, http) once for the app

Define Service

class UserRepo extends Effect.Service<UserRepo>()("UserRepo", {
  sync: () => ({ find: (id: string) => Effect.succeed({ id }) })
}) {}

Provide Layer

const program = Effect.gen(function* () {
  const repo = yield* UserRepo
  return yield* repo.find("123")
}).pipe(Effect.provide(UserRepo.Default))

Compose

const AppLayer = Layer.merge(UserRepo.Default, Logger.Default)

Test vs Live

const layer = process.env.NODE_ENV === "test" ? UserRepoTest : UserRepo.Default

Guidance

  • Services define interfaces; Layers bind implementations
  • Compose layers at the app boundary; keep handlers unaware of wiring
  • Use .Default for quick live/test setup; add custom layers as needed

Pitfalls

  • Circular layer dependencies → split modules, provide from above
  • Providing layers too deep → centralize to avoid duplication and confusion

Local Source Reference

CRITICAL: Search local Effect source before implementing

The full Effect source code is available at docs/effect-source/. Always search the actual implementation before writing Effect code.

Key Source Files

  • Layer: docs/effect-source/effect/src/Layer.ts
  • Effect: docs/effect-source/effect/src/Effect.ts
  • Context: docs/effect-source/effect/src/Context.ts

Example Searches

# Find Layer composition patterns
grep -F "Layer.merge" docs/effect-source/effect/src/Layer.ts
grep -F "Layer.provide" docs/effect-source/effect/src/Layer.ts

# Study Effect.Service patterns
grep -F "Effect.Service" docs/effect-source/effect/src/Effect.ts

# Find Context usage
grep -F "Tag" docs/effect-source/effect/src/Context.ts
grep -F "make" docs/effect-source/effect/src/Context.ts

# Look at Layer test examples
grep -F "Layer." docs/effect-source/effect/test/Layer.test.ts

Read the full file on GitHub · 93 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. 2mo ago First seen · 93 lines · 27 tokens per session scan A e1710922ad9a

Subscribe to this mod's changes

effect-layers-services is a skill published in the GitHub repository mepuka/effect-ontology (5 stars, last pushed 10mo ago), licensed MIT. It adds 27 tokens to every session and 696 once invoked, about $0.0001 per session on Opus 5.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-31.

Related

effect-layers-services compared with skills from other repositories

effect-layers-services next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
effect-layers-servicesmepuka/effect-ontologySkill510mo agoMITA27Claude Code
mem0-oss-to-platformmem0ai/mem0Skill68k2d agoApache-2.0A217Claude Code, Codex
azure-mgmt-botservice-dotnetmicrosoft/skillsSkill3.2kyesterdayMITA78Claude Code
fastapi-router-pymicrosoft/skillsSkill3.2kyesterdayMITA46Claude Code
dev-runtimelangwatch/langwatchSkill5.0kyesterdayApache-2.0A172Claude Code
api-designericrisco/rsc-harnessSkill5032d agoMITA105Claude Code, Codex
migrate-segw-to-raparc-mcp/arc-1Skill252yesterdayMITA106Claude Code