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-graphnpx skills add mpsuesser/pi-effect-harness --skill effect-graphgit 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-graph)<a href="https://agentmods.dev/skills/mpsuesser/pi-effect-harness/effect-graph"><img src="https://agentmods.dev/badge/skills/mpsuesser/pi-effect-harness/effect-graph.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.00102 | $0.06373 |
| Opus 5 | $0.00051 | $0.03187 |
| Sonnet 5 | $0.00020 | $0.01275 |
| Haiku 4.5 | $0.00010 | $0.00637 |
Grade A, and why
effect-graph 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 — 502 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 the Graph module — building, querying, traversing, and running algorithms over immutable graphs.
Effect Source Reference
The Effect v4 source is at ~/.cache/effect-v4/. Read it directly when in doubt — the module is self-contained in a single file.
Key files:
packages/effect/src/Graph.ts— the entire module: types, constructors, mutation scope, queries, walkers, traversals, algorithms, GraphViz/Mermaid exportpackages/effect/test/Graph.test.ts— edge-case semantics: multi-edges, self-loops, undefined node/edge data, negative-weight behavior, walker re-iteration, topoinitials
Core Model
A Graph<N, E, T extends Kind = 'directed'> is an immutable graph storing user data N on nodes and E on edges, where T is 'directed' | 'undirected'. Writes only happen on a MutableGraph<N, E, T> inside an explicit mutation scope; everything else (queries, traversals, algorithms) accepts either form.
import { Graph, Option } from 'effect';
// or as a subpath module:
import * as Graph from 'effect/Graph';
The pieces:
Graph.NodeIndex/Graph.EdgeIndex— plainnumberidentifiers. They are allocated sequentially from0and never reused after removal; they are stable IDs, not array offsets.Graph.Edge<E>— aData.Classwith{ source: NodeIndex; target: NodeIndex; data: E }.Graph.DirectedGraph<N, E>/Graph.UndirectedGraph<N, E>— aliases forGraph<N, E, 'directed' | 'undirected'>;MutableDirectedGraph/MutableUndirectedGraphare the mutable counterparts.Graph.GraphError— aData.TaggedError('GraphError')<{ message: string }>. The Graph API is fully synchronous: nothing returnsEffect. Invalid operations throwGraphError; lookups returnOption.Graph.Walker<T, N>— the lazy iterator wrapper returned by all traversal and listing APIs.
Call conventions:
- Read APIs are dual (data-first or pipeable data-last):
Graph.neighbors(graph, 0)orgraph.pipe(Graph.neighbors(0)). - Write APIs are data-first only and take the
MutableGraphas the first argument:Graph.addNode(mutable, data). - Graphs implement
Equal,Hash,Pipeable,Inspectable, and are iterable over[NodeIndex, N]node entries.
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 · 502 lines · 102 tokens per session scan A 3dfce5dca0e6
effect-graph is a skill published in the GitHub repository mpsuesser/pi-effect-harness (24 stars, last pushed 2mo ago), licensed MIT. It adds 102 tokens to every session and 6,373 once invoked, about $0.0005 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-making-http-requests
Effect-TS patterns for Making Http Requests. Use when working with making http requests in Effect-TS applications.
effect-patterns-streams
Effect-TS patterns for Streams. Use when working with streams 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-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.