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-pubsub-event-busgit 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-pubsub-event-bus)<a href="https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-pubsub-event-bus"><img src="https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-pubsub-event-bus/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/skills/mpsuesser/pi-effect-harness/effect-pubsub-event-bus"><img src="https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-pubsub-event-bus.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.00047 | $0.02736 |
| Opus 5 | $0.00023 | $0.01368 |
| Sonnet 5 | $0.00009 | $0.00547 |
| Haiku 4.5 | $0.00005 | $0.00274 |
Grade A, and why
effect-pubsub-event-bus 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 10d 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 — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PubSub Event Bus with Effect v4
Overview
Effect's PubSub module provides a typed, composable publish/subscribe primitive. Combined with Stream.fromPubSub and Effect.forkScoped, it replaces imperative callback-based event buses with a fully typed, stream-based subscription model where cleanup is automatic.
When to use this skill:
- Building intra-service communication (event bus, message broker)
- Replacing callback-based event systems with typed streams
- Implementing reactive patterns where services subscribe to domain events
- Managing per-instance event channels with scoped cleanup
Import Pattern
import { Effect, PubSub, Stream } from 'effect';
Core Pattern: Typed Event Bus Service
Define events as a discriminated union, then build a Bus service that publishes and subscribes using PubSub:
import { Effect, Layer, PubSub, Schema, Context, Stream } from 'effect';
// ─── Event Definitions ──────────────────────────────────────
class FileChanged extends Schema.TaggedClass<FileChanged>()('FileChanged', {
path: Schema.String,
kind: Schema.Literals(['created', 'modified', 'deleted'])
}) {}
class ConfigReloaded extends Schema.TaggedClass<ConfigReloaded>()(
'ConfigReloaded',
{
source: Schema.String
}
) {}
type BusEvent = FileChanged | ConfigReloaded;
// ─── Bus Service ─────────────────────────────────────────────
export namespace Bus {
export interface Interface {
readonly publish: (event: BusEvent) => Effect.Effect<void>;
readonly subscribe: <T extends BusEvent>(
eventClass: new (...args: ReadonlyArray<never>) => T
) => Stream.Stream<T>;
readonly subscribeAll: Stream.Stream<BusEvent>;
}
export class Service extends Context.Service<Service, Interface>()(
'@app/Bus'
) {}
export const layer = Layer.effect(
Service,
Effect.gen(function* () {
const pubsub = yield* PubSub.unbounded<BusEvent>();
// Cleanup: shutdown PubSub when scope closes
yield* Effect.addFinalizer(() => PubSub.shutdown(pubsub));
const publish = Effect.fn('Bus.publish')(function* (
event: BusEvent
) {
yield* PubSub.publish(pubsub, event);
});
const subscribe = <T extends BusEvent>(
eventClass: new (...args: ReadonlyArray<never>) => T
): Stream.Stream<T> =>
Stream.fromPubSub(pubsub).pipe(
Stream.filter((evt): evt is T => evt instanceof eventClass)
);
const subscribeAll = Stream.fromPubSub(pubsub);
return Service.of({ publish, subscribe, subscribeAll });
})
);
}
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.
- 10d ago First seen · 358 lines · 47 tokens per session scan A 2f2d1bb240e0
effect-pubsub-event-bus is a skill published in the GitHub repository mpsuesser/pi-effect-harness (24 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 2,736 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-making-http-requests
Effect-TS patterns for Making Http Requests. Use when working with making http requests 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-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.