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-testingnpx skills add mpsuesser/pi-effect-harness --skill effect-testinggit 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-testing)<a href="https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-testing"><img src="https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-testing.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.00049 | $0.08499 |
| Opus 5 | $0.00024 | $0.04249 |
| Sonnet 5 | $0.00010 | $0.01700 |
| Haiku 4.5 | $0.00005 | $0.00850 |
Grade A, and why
effect-testing 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 4d 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 — 1,262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Effect Testing Skill
This skill provides comprehensive guidance for testing Effect-based applications using @effect/vitest and standard vitest.
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:
- Testing utilities:
packages/effect/src/Testing.ts - @effect/vitest source:
packages/vitest/ - Migration guide:
MIGRATION.md - Effect source:
packages/effect/src/
Framework Selection
CRITICAL: Choose the correct testing framework based on the code being tested.
Use @effect/vitest for Effect Code
Use @effect/vitest when testing:
- Functions that return
Effect<A, E, R> - Code that uses services and layers
- Time-dependent operations with
TestClock - Asynchronous operations coordinated with Effect
- STM (Software Transactional Memory) operations
import { it, expect } from '@effect/vitest';
import { Effect } from 'effect';
declare const fetchUser: (id: string) => Effect.Effect<{ id: string }, Error>;
it.effect('should fetch user', () =>
Effect.gen(function* () {
const user = yield* fetchUser('123');
expect(user.id).toBe('123');
})
);
Use Regular vitest for Pure Functions
Use standard vitest for:
- Pure functions with no Effect wrapper
- Simple data transformations
- Helper utilities
- Type constructors (brands, newtypes)
import { describe, expect, it } from 'vitest';
declare const Cents: {
make: (value: bigint) => bigint;
add: (a: bigint, b: bigint) => bigint;
};
describe('Cents', () => {
it('should add cents correctly', () => {
const result = Cents.add(Cents.make(100n), Cents.make(50n));
expect(result).toBe(150n);
});
});
Test Variants
it.effect - Default Test Environment
Provides TestContext including TestClock, TestRandom, etc.
import { it, expect } from '@effect/vitest';
import { Effect } from 'effect';
declare const someEffect: Effect.Effect<number>;
declare const expected: number;
it.effect('test name', () =>
Effect.gen(function* () {
// Test implementation with TestContext available
const result = yield* someEffect;
expect(result).toBe(expected);
})
);
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.
- 4d ago First seen · 1,262 lines · 49 tokens per session scan A 1053b3eb5ff1
effect-testing is a skill published in the GitHub repository mpsuesser/pi-effect-harness (23 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 8,499 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-building-apis
Effect-TS patterns for Building Apis. Use when working with building apis in Effect-TS applications.
effect-patterns-concurrency
Effect-TS patterns for Concurrency. Use when working with concurrency 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-error-management
Effect-TS patterns for Error Management. Use when working with error management 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-observability
Effect-TS patterns for Observability. Use when working with observability in Effect-TS applications.