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-v3-to-v4/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-v3-to-v4)<a href="https://agentmods.dev/skills/lodyai/lody/effect-v3-to-v4"><img src="https://agentmods.dev/badge/skills/lodyai/lody/effect-v3-to-v4/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-v3-to-v4"><img src="https://agentmods.dev/badge/skills/lodyai/lody/effect-v3-to-v4.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.00044 | $0.02465 |
| Opus 5.5 | $0.00018 | $0.00986 |
| Sonnet 5.5 | $0.00009 | $0.00493 |
| Haiku 4.5 | $0.00004 | $0.00247 |
Grade A, and why
effect-v3-to-v4 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 22d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lody overrides (read first)
These repository rules override the upstream steps below.
- Keep the workspace catalog and lockfile version. Do not run
effect@latest, add a root dependency, or upgrade packages as a side effect of this skill. Version changes require an explicit task. - Resolve Effect from the package being changed, not an arbitrary root or
transitive installation. Read its
effect/AGENTS.mdcompletely and follow the required links; search itsai-docsandsrcon demand. If dependencies are absent, follow repository installation rules. A temporary copy of the exact locked npm release is a read-only reference, not local validation. Upstream main is not the installed API. - Read Lody's Effect guide and applicable scoped
AGENTS.md. Give tasks and resources an explicit Scope owner, propagate cancellation across Promise boundaries, await cleanup, and bound finalizer waits. Temporary Promise facades needLegacynames and@deprecated. - Type-checking alone is not acceptance. For shutdown, cancellation, resource release, retry or synchronization changes, run owning behavioral tests, including failure paths, with explicit signals and injected/fake clocks. Report baseline failures and environment limits separately; do not weaken tests.
- Preserve the public/local boundary and disabled telemetry when using upstream
examples. Edit
AGENTS.mdonly;CLAUDE.mdis its symlink. - Lody is already on v4. Apply this skill only to an explicitly scoped migration; do not force third-party transitive v3 consumers onto v4.
- Fetch supplementary upstream guides/tests only as needed, outside tracked project files. Pin v4 sources to the target release tag/commit and verify API signatures against the actual dependency. Check ownership and local changes before replacing a pre-existing checkout. The upstream "tests are not a gate" completion rule below does not apply to Lody.
Effect v3 to v4 Migration
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.
- 22d ago First seen · 142 lines · 44 tokens per session scan A 5290a5aa5cee
effect-v3-to-v4 is a skill published in the GitHub repository LodyAI/Lody (1,640 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 2,465 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-11.
Other skills, from other repositories
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.
ruff
Use when the user lints or formats Python code from the command line. ruff is a 2-in-1 tool - ruff check runs the linter (rules / fixes / import sort / security), and ruff format runs the formatter (Black-compatible style rewrites). They are distinct subcommands...
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…
omk-code-review
Review implementation changes against contracts and real failure modes, preserve minimal patches, and verify regressions without confusing test counts, generated code volume or CI claims with production correctness.
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.'.
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…