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 agentmods add skills/mpsuesser/pi-effect-harness/effect-workflownpx skills add mpsuesser/pi-effect-harness --skill effect-workflowgit 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-workflow)<a href="https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-workflow"><img src="https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-workflow.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 | $0.00045 | $0.05958 |
| Opus 5 | $0.00023 | $0.02979 |
| Sonnet 5 | $0.00009 | $0.01192 |
| Haiku 4.5 | $0.00005 | $0.00596 |
Grade A, and why
effect-workflow 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 5d 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 — 803 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Effect TypeScript expert specializing in durable workflow execution using the effect/unstable/workflow module.
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.
Key source files:
packages/effect/src/unstable/workflow/Workflow.ts— Workflow definition, compensation, annotationspackages/effect/src/unstable/workflow/Activity.ts— Activity definition, retry, idempotencypackages/effect/src/unstable/workflow/WorkflowEngine.ts— Engine service, in-memory layer, encoded interfacepackages/effect/src/unstable/workflow/DurableClock.ts— Durable sleep/timerspackages/effect/src/unstable/workflow/DurableDeferred.ts— Durable signal/wait, tokens, done/succeed/failpackages/effect/src/unstable/workflow/DurableQueue.ts— Durable queue handing work to persisted background workers
IMPORTANT: Unstable API
The workflow module lives under effect/unstable/workflow. APIs may change between versions. All imports use this path:
import {
Workflow,
Activity,
WorkflowEngine,
DurableClock,
DurableDeferred,
DurableQueue
} from 'effect/unstable/workflow';
Core Concepts
Effect Workflow provides durable execution — workflows that survive process restarts through event sourcing. The key idea: activities are the units of side-effectful work whose results get persisted. On replay, persisted results are returned without re-executing the activity.
Architecture
Workflow → defines the overall process (name, payload, success/error schemas)
Activity → a discrete unit of work inside a workflow (results are persisted)
WorkflowEngine → orchestrates execution, replay, suspension, resumption
DurableClock → sleep/timer that persists across restarts
DurableDeferred → wait-for-external-signal that persists across restarts
DurableQueue → hand work to a persisted background worker and await its result
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.
- 5d ago First seen · 803 lines · 45 tokens per session scan A 55c3f7efcf85
effect-workflow is a skill published in the GitHub repository mpsuesser/pi-effect-harness (24 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 5,958 once invoked, about $0.0002 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-streams
Effect-TS patterns for Streams. Use when working with streams 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-sinks
Effect-TS patterns for Streams Sinks. Use when working with streams sinks 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-resource-management
Effect-TS patterns for Resource Management. Use when working with resource management in Effect-TS applications.