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.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/instructions/lodyai/lody/agents-md)<a href="https://agentmods.dev/instructions/lodyai/lody/agents-md"><img src="https://agentmods.dev/badge/instructions/lodyai/lody/agents-md/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/instructions/lodyai/lody/agents-md"><img src="https://agentmods.dev/badge/instructions/lodyai/lody/agents-md.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.01966 | $0.01966 |
| Opus 5.5 | $0.00786 | $0.00786 |
| Sonnet 5.5 | $0.00393 | $0.00393 |
| Haiku 4.5 | $0.00197 | $0.00197 |
Grade A, and why
Lody AGENTS.md 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 4d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository rules
CLAUDE.md is a symlink to this file. Edit AGENTS.md only.
Map: README.md.
Context and documentation
- Read the applicable ancestor/scoped
AGENTS.mdfiles and task-relevant Specs,.agents/docs/, and module READMEs, then the notes they link for the rationale. Search notes directly before reversing a recorded decision. Follow the required topic links below when their trigger applies, including changes outside the owner's directory. Archives are history, not current authority. - A note you rely on that is stale, unlinked, or in the wrong lifecycle is fixed in the same PR (maintenance on read).
- Specs express intent, docs explain implementation, notes record decisions. Distinguish bugs, stale docs, and unimplemented intent using code and evidence; never change a Spec to justify a bug.
- Before creating or editing a Spec, read Spec rules, including status and approval requirements. Reserve Specs for consequential decisions needing human review; prefer an existing Spec. Ordinary fixes need no new Spec.
- Add/update an Agent Note in the same PR only for durable rationale: alternatives, unenforceable constraints, measurements, formats or ownership. A fix that is merely done belongs in its PR and test. Every new note runs the supersession check; keep implemented notes' cited facts current. Report deferred notes for read-only work.
- Update affected docs/READMEs. Run
pnpm run docs statusat start andpnpm run docs checkat finish; review SHA-protected changes before confirming. Checks and translations establish neither correctness nor approval; translation may follow later. See document maintenance. - Keep PR docs compact: consolidate decisions, evidence and limits; avoid fix/run logs. Follow submission consolidation.
- Keep binding rules in the nearest
AGENTS.mdas complete sentences (new scopes need aCLAUDE.mdsymlink); over a word ceiling, relocate a topic or raise the ceiling with a reason, never compress into fragments. Keep explanations and rationale in their owning docs/notes.
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.
- 4d ago Changed · +6 lines · +120 tokens per session 9368e54128ea
- 7d ago Changed · +2 tokens per session 393790e0087d
- 10d ago Changed · +21 tokens per session 4adae0836688
- 15d ago Changed · -2 lines · -21 tokens per session 32f13f58cf15
- 19d ago Changed · +3 lines · +38 tokens per session ed9efbea49f3
- 20d ago Changed · -3 tokens per session 5deff740797f
- 21d ago Changed · +14 lines · +241 tokens per session e6d916ee0b70
- 22d ago Changed · +11 lines · +133 tokens per session 57de059ad30b
- 1mo ago Changed · +1 lines 2c7495a34167
- 1mo ago First seen · 96 lines · 1,435 tokens per session scan A e03c58bfda08
Lody AGENTS.md is an instructions file published in the GitHub repository LodyAI/Lody (1,640 stars, last pushed today), licensed Apache-2.0. It adds 1,966 tokens to every session, about $0.0079 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-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.