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 jpoehnelt/skills --skill effect-seam-migrationgit clone --depth 1 https://github.com/jpoehnelt/skillsWrote 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/jpoehnelt/skills/effect-seam-migration)<a href="https://agentmods.dev/skills/jpoehnelt/skills/effect-seam-migration"><img src="https://agentmods.dev/badge/skills/jpoehnelt/skills/effect-seam-migration/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/jpoehnelt/skills/effect-seam-migration"><img src="https://agentmods.dev/badge/skills/jpoehnelt/skills/effect-seam-migration.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.00059 | $0.00651 |
| Opus 5.5 | $0.00024 | $0.00260 |
| Sonnet 5.5 | $0.00012 | $0.00130 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
effect-seam-migration 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 9d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Effect-seam runtime migration
Separate extraction from the runtime move so each step preserves behavior. Never register unextracted app code on a new runtime. Use effect for runners and layers. Assumes Effect v4.
Repo facts (from AGENTS.md): where packages live, the runtimes and their entrypoints, any workflow ownership catalog or manifest assertion, shared event contracts, Effect gates, and check, test, and local-run commands.
Extract (finish first)
- Identify the workload: entry point, callers, dependencies, resource lifetime. Record implicit authorization, tenant scoping, ordering, deduplication, retry identity, and error behavior.
- Move app-independent logic into an owning package. Pure synchronous logic stays outside Effect; I/O is exposed as Effect programs with service dependencies in
R. Packages never import an app. - Move the unit's tests into the package. Only route, transport, and runtime-boundary integration tests stay beside the app.
- Keep execution on the existing runtime until focused checks and the existing integration path pass. Keep the repo's Effect gates (round-trip, thin-wrapper, runtime-exit checks) green.
Move (after extraction)
- Compose the required layers at the destination entry point and run programs only through its boundary runner.
- Establish exactly one execution owner. If the repo has an ownership catalog or manifest, add the unit there and register it on the new runtime in the same change.
- Delete the old runtime's shell, callers, and execution path in the change that activates the replacement, one unit at a time. No fallback, catch-and-retry, or failover to the old runtime when the new one times out or errors; rely on the durable retry layer.
- Keep cross-runtime event names and schemas in the existing shared contract. You are moving execution, not rebuilding plumbing.
- Update exports, dependency manifests, build-task inputs, deployment declarations, and generated artifacts together. Use
eng-cutover-verificationto prove the old path is gone.
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.
- 9d ago First seen · 37 lines · 59 tokens per session scan A e8666333f703
effect-seam-migration is a skill published in the GitHub repository jpoehnelt/skills (23 stars, last pushed 3d ago), licensed MIT. It adds 59 tokens to every session and 651 once invoked, about $0.0002 per session on Opus 5.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-10-21.
Other skills, from other repositories
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
django-storages-s3
Use when configuring Django to store static and media files on AWS S3 with django-storages. Invoke when working with the STORAGES setting, S3 buckets, presigned URLs, CloudFront, or boto3-backed file storage in settings.py. Configures the Django 4.2+ STORAGES dict, public/private custom backends, presigned GET/POST…
websocket-engineer
Use when building real-time communication systems with WebSockets or Socket.IO. Invoke for bidirectional messaging, horizontal scaling with Redis, presence tracking, room management.
azure-eventhub-dotnet
Azure Event Hubs SDK for .NET. Use for high-throughput event streaming: sending events (EventHubProducerClient, EventHubBufferedProducerClient), receiving events (EventProcessorClient with checkpointing), partition management, and real-time data ingestion. Triggers: "Event Hubs", "event streaming"…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
wikipedia
Search and read Wikipedia via x wkp — MediaWiki API, no API key, zero install; query, extract, suggest, and DDG route in one module. Load for wiki, wikipedia, encyclopedia lookup, article summary.