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-observabilitygit 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-observability)<a href="https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-observability"><img src="https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-observability.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.00044 | $0.04849 |
| Opus 5 | $0.00022 | $0.02424 |
| Sonnet 5 | $0.00009 | $0.00970 |
| Haiku 4.5 | $0.00004 | $0.00485 |
Grade A, and why
effect-observability 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 — 703 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 observability — structured logging, distributed tracing, and metrics collection.
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:
Loggermodule:packages/effect/src/Logger.tsTracermodule:packages/effect/src/Tracer.tsMetricmodule:packages/effect/src/Metric.ts- OTLP export:
packages/effect/src/unstable/observability/ - Observability examples:
ai-docs/src/08_observability/
1. Structured Logging
Log Functions
Effect provides log functions at every level. Each is variadic and accepts one or more message values:
import { Effect } from 'effect';
const program = Effect.gen(function* () {
yield* Effect.log('general log message');
yield* Effect.logDebug('debug-level detail');
yield* Effect.logInfo('informational message');
yield* Effect.logWarning('something concerning');
yield* Effect.logError('something failed');
});
Pass additional message values after the first. These extra values become part of the log message/body — they are not automatically indexed as queryable annotations:
yield* Effect.log('User action', { userId: 123, action: 'login' });
yield* Effect.logInfo('Request processed', { duration: 150, statusCode: 200 });
For queryable dimensions (fields you want to filter or group on in your logging/tracing backend), prefer Effect.annotateLogs or span annotations (Effect.annotateCurrentSpan / Effect.annotateSpans) rather than passing objects as message values.
Log Annotations
Attach key-value metadata to all log lines within a scope:
const checkout = Effect.gen(function* () {
yield* Effect.logInfo('validating cart');
yield* Effect.logWarning('inventory low for one line item');
yield* Effect.logError('payment provider timeout');
}).pipe(
Effect.annotateLogs({
service: 'checkout-api',
route: 'POST /checkout'
})
);
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 · 703 lines · 44 tokens per session scan A 7c477aae93f3
effect-observability is a skill published in the GitHub repository mpsuesser/pi-effect-harness (24 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 4,849 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-building-data-pipelines
Effect-TS patterns for Building Data Pipelines. Use when working with building data pipelines 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-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-resource-management
Effect-TS patterns for Resource Management. Use when working with resource management in Effect-TS applications.