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/lody-cli/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/lody-cli)<a href="https://agentmods.dev/skills/lodyai/lody/lody-cli"><img src="https://agentmods.dev/badge/skills/lodyai/lody/lody-cli/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/lody-cli"><img src="https://agentmods.dev/badge/skills/lodyai/lody/lody-cli.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.00103 | $0.06205 |
| Opus 5.5 | $0.00041 | $0.02482 |
| Sonnet 5.5 | $0.00021 | $0.01241 |
| Haiku 4.5 | $0.00010 | $0.00620 |
Grade A, and why
lody-cli 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 3d 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 — 417 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lody CLI
This guide covers the cloud edition of Lody, including its account sign-in and shared workspaces. The open-source local edition is outside this guide's scope; do not apply these sign-in prerequisites to it.
How to call it
- Installed globally (
npm i -g lody): runlody …. - Without installing: run
npx lody …. Everylodycommand in this guide works the same way with thenpxprefix. Inside scripts, usenpx -y lody …to skip the install prompt. - Requires Node.js 22.14+ (22.x) or 23.6+.
- Check which one is available with
lody --versionornpx -y lody --version, and stick to that form for the whole task.
lody does two jobs. It runs the Lody runtime that executes agents on this machine
(start, daemon). It also works as a one-shot client for workspace resources: sessions,
schedules, agent configs, Roles, MCP servers and projects. Exact flags come from
built-in help: lody <group> [<sub>] --help. This guide covers what help leaves out:
prerequisites, shared conventions, business rules and the actions to confirm first.
Before running anything
- Sign in when required. Reuse an existing login; if a command reports missing or
invalid Lody credentials, do not run a bare
lody loginfrom an agent. It waits for browser authorization and can block without visible output when stdout is not a terminal. Have the user runlody loginin their terminal, or uselody login --auth <key>with a CLI API key or machine connection token the user provides. Workspaces, sessions, agent configs and machines are shared across every machine signed in to the same account. - Runtime. Commands that run agents on this machine need the Lody runtime. Start it
in the foreground with
lody startor in the background withlody daemon start.- If it is not running, the command fails and says so. Start the runtime first.
- If it is busy, retry later.
- Each machine has only one runtime. When the Lody desktop app is open, it already owns
the runtime and
lody start/daemon startrefuse to start another. That is expected: the CLI uses the app's runtime.
- Where you are calling from.
- Inside a Lody session, the agent's environment has
LODY_SESSION_ID, and usuallyLODY_WORKSPACE_IDandLODY_AGENT_CONFIG_ID. Many commands use these when you leave the matching argument out:- the session commands'
sessionId operation list --sessionagent-role create/update --session--use-current-session-as-parentand--opened-by-current
- the session commands'
- Inside a Lody session, the agent's environment has
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.
- 3d ago Changed · -6 lines 28522f0f9b4f
- 10d ago First seen · 423 lines · 103 tokens per session scan A 8818ba76692c
lody-cli is a skill published in the GitHub repository LodyAI/Lody (1,640 stars, last pushed today), licensed Apache-2.0. It adds 103 tokens to every session and 6,205 once invoked, about $0.0004 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-23.
Other skills, from other repositories
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
subscription-setup
A setup workflow for creating recurring medical-learning subscriptions after a doctor’s profile has been registered.
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…
ponytail-gain
Show ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /ponytail-gain, "ponytail gain", "what does ponytail save", "show ponytail impact", "ponytail scoreboard".
automation
Instructions for managing scheduled tasks through the host's structured automation tool, including reminders, delayed work, recurring checks, and result delivery.
cron
Schedule, list, pause, resume, edit, or run the user's agentica cron jobs with the cronjob tool. Use when asked to remind, schedule a recurring or one-shot task, try a job now, or manage jobs that fire unattended.