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.
git clone --depth 1 https://github.com/PaulJPhilp/EffectPatternsWrote 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/rules/pauljphilp/effectpatterns/create-a-reusable-runtime-from-layers)<a href="https://agentmods.dev/rules/pauljphilp/effectpatterns/create-a-reusable-runtime-from-layers"><img src="https://agentmods.dev/badge/rules/pauljphilp/effectpatterns/create-a-reusable-runtime-from-layers/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.
<a href="https://agentmods.dev/rules/pauljphilp/effectpatterns/create-a-reusable-runtime-from-layers"><img src="https://agentmods.dev/badge/rules/pauljphilp/effectpatterns/create-a-reusable-runtime-from-layers.svg" alt="Reviewed on agentmods" width="80" 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.00215 | $0.00215 |
| Opus 5.5 | $0.00086 | $0.00086 |
| Sonnet 5.5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
create-a-reusable-runtime-from-layers 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 1mo 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.
What it actually says
description: Create a reusable runtime from layers. globs: "**/*.ts" alwaysApply: true
Create a Reusable Runtime from Layers
Rule: Create a reusable runtime from layers.
Example
import { Effect, Layer, Runtime } from "effect";
class GreeterService extends Effect.Service<GreeterService>()("Greeter", {
sync: () => ({
greet: (name: string) => Effect.sync(() => `Hello ${name}`),
}),
}) {}
const runtime = Effect.runSync(
Layer.toRuntime(GreeterService.Default).pipe(Effect.scoped)
);
// In a server, you would reuse `run` for every request.
Runtime.runPromise(runtime)(Effect.log("Hello"));
Explanation:
By compiling your layers into a Runtime once, you avoid rebuilding the
dependency graph for every effect execution.
Explanation:
Building the dependency graph from layers has a one-time cost. Creating a
Runtime once when your application starts is highly efficient for
long-running applications.
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.
- 1mo ago First seen · 34 lines · 215 tokens per session scan A f7b254a7f25c
create-a-reusable-runtime-from-layers is a cursor rule published in the GitHub repository PaulJPhilp/EffectPatterns (807 stars, last pushed 4mo ago), licensed MIT. It adds 215 tokens to every session, about $0.0009 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-09-03.
Other cursor rules, from other repositories
django-python
Rules for writing Python services at PostHog (Python servers powered by the Django framework).
python--typescript-guide-cursorrules-prompt-file
Cursor rules for Python development with TypeScript guide integration.
standard-nestjs-module-hierarchy
Establish a consistent NestJS module structure in the API application where each resource is encapsulated in its own module with proper hierarchical organization to enhance maintainability, scalabilit... .
nestjs-best-practices
../../.claude/rules/nestjs-best-practices.md.
nestjs
This guide provides opinionated, actionable best practices for building robust, scalable, and maintainable NestJS applications using TypeScript, emphasizing modern patterns and common pitfalls.
nodejs-best-practices
Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.