Lody is a shared workspace that connects coding agents running on different computers and lets people view and direct their work from desktop, mobile, web, or a command line. Teams use it to share agent conversations, monitor progress and code changes, and assign work to connected machines while retaining their existing agents and configurations.
Borrowing it
Nothing to install: this file belongs to LodyAI/Lody. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/LodyAI/Lody/main/.agents/skills/effect-ts/SKILL.mdgit clone --depth 1 https://github.com/LodyAI/LodyWrote 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/lodyai/lody/effect-ts)<a href="https://agentmods.dev/skills/lodyai/lody/effect-ts"><img src="https://agentmods.dev/badge/skills/lodyai/lody/effect-ts/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/lodyai/lody/effect-ts"><img src="https://agentmods.dev/badge/skills/lodyai/lody/effect-ts.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.00030 | $0.01240 |
| Opus 5.5 | $0.00012 | $0.00496 |
| Sonnet 5.5 | $0.00006 | $0.00248 |
| Haiku 4.5 | $0.00003 | $0.00124 |
Grade A, and why
effect-ts 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 21d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Native Effect work in Lody
Use this skill before assessing a native migration, choosing its structure or changing Effect lifecycle behavior. Lody already uses v4; ordinary Promise-to-Effect refactoring does not invoke the v3-to-v4 skill. Use that skill only for an explicitly scoped version migration.
Resolve the reference and scope
Select the task mode before migration planning:
| Request | Work and stopping condition |
|---|---|
| Review | Trace changed behavior against the base and applicable contracts; report only findings allowed by repository review rules. Do not start a migration. |
| Debug | Reproduce the symptom, isolate the cause and distinguish raw work from its waiter; diagnosis alone does not authorize a rewrite. |
| Feature/fix | Deliver the requested behavior; include a complete native unit only when its dependencies and verification fit the task. Deferring migration is a valid outcome. |
| Dedicated migration | Trace the complete responsibility and consumers; apply all three completion axes: kernel, consumers and ownership. |
Keep the workspace catalog and lockfile version. Follow repository installation
rules if dependencies are missing; do not install latest, add a root dependency
or upgrade packages as a side effect. Resolve Effect from the consuming package,
read its effect/AGENTS.md completely once per resolved version in the current
context, then follow task-relevant links. Re-read if the version or context is lost.
Search that release's ai-docs and src for APIs and lifecycle semantics. Upstream
main and a temporary exact-release reference are not local validation.
Read applicable scoped AGENTS.md and relevant sections of Lody's Effect guide. For migration scope or completion claims, consult the relevant charter and ledger rows and their owning Notes; a whole-roadmap reread is unnecessary. Retain existing product contracts, pure computation, public/local boundaries and disabled telemetry. Upstream Schema, SQL and CLI examples do not authorize replacing Lody's existing validation, persistence or command frameworks.
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.
- 21d ago Changed · +37 lines · +8 tokens per session fdcf237e4e72
- 22d ago First seen · 61 lines · 22 tokens per session scan A 8fd5d4efb125
effect-ts is a skill published in the GitHub repository LodyAI/Lody (1,640 stars, last pushed today), licensed Apache-2.0. It adds 30 tokens to every session and 1,240 once invoked, about $0.0001 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-11.
Other skills, from other repositories
bun
Read before a js eval cell that spawns a process, server or PTY, installs a package, or starts a long run, and before any bun -e, script, server, CLI, test, typecheck, format, bundle, or package-management work: this session's eval js kernel runs Bun 1.4+. Bun 1.4.x builtins replace 20+ npm deps and dev tools — check…
V3 Core Implementation
Core module implementation for claude-flow v3. Implements DDD domains, clean architecture patterns, dependency injection, and modular TypeScript codebase with comprehensive testing.
pstack-principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
pstack-principle-prove-it-works
Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'.
pstack-principle-type-system-discipline
Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, exhaust variants, derive from authoritative schemas.
pi
Use when you need a minimal, extensible terminal AI coding agent harness in TypeScript — npm @earendil-works/pi-coding-agent 1.4.0, extensions/skills/prompt templates, multi-provider (OpenAI/Anthropic/Google) routing, container isolation (Docker/Gondolin/OpenShell); also for pi: command not found, Node >=22.19.0…