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/archive-agent-notes/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/archive-agent-notes)<a href="https://agentmods.dev/skills/lodyai/lody/archive-agent-notes"><img src="https://agentmods.dev/badge/skills/lodyai/lody/archive-agent-notes/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/archive-agent-notes"><img src="https://agentmods.dev/badge/skills/lodyai/lody/archive-agent-notes.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.00073 | $0.01309 |
| Opus 5.5 | $0.00029 | $0.00524 |
| Sonnet 5.5 | $0.00015 | $0.00262 |
| Haiku 4.5 | $0.00007 | $0.00131 |
Grade A, and why
archive-agent-notes 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archive Lody Agent Notes
Notes are the repository's decision memory. This workflow keeps the active set
(proposed/ and implemented/) small enough to search and current enough to
trust, without losing history that can still guide work. Judge every note by its
future decision value. Word count, age and inbound-link count are discovery aids,
never criteria, and there is no quota.
Read the contracts
Read the note rules and document maintenance.
Establish whether a rationale still owns or constrains anything from current code,
Specs, .agents/docs/, owning READMEs, newer notes and inbound links, not from
the note's own claims.
Supersession check for a new note
Run this before drafting any note, scoped to the decision being recorded:
- Search active notes for the same decision, mechanism, file paths and rejected
alternatives. Search titles and abstracts first;
git log --name-onlyon the changed source paths finds notes committed with earlier changes to them. - If one note already owns the decision, update it. Do not create a second note.
- For each implemented note the new decision fully replaces, carry every unique
rationale, alternative, measurement and reintroduction condition into the new
note, archive the old pair, and list it under
Supersedes:in the new note's metadata, linking the archived path. - For a partial replacement, keep both active, cross-link them, and correct the facts in the older note that the change made stale.
- Reject a proposal the new decision makes obsolete; never archive a proposal.
Do not defer a known match to a later audit.
Classify by future value
Apply these outcomes per lifecycle:
- Implemented, delete: the note records only a small UI adjustment, a local interaction fix or a purely mechanical change. Delete both languages and repair or remove inbound links. Apply this test first.
- Implemented, keep active: its rationale, rejected alternatives, negative guarantee, durable or wire semantics, ownership boundary, security rule, measurement or reintroduction condition is likely to guide a future change. Classify the decision, not the size of its implementation.
- Implemented, archive: a substantive decision that is complete and unlikely to guide future work, but whose rationale still has historical value.
- Proposed, reject: the work is no longer worth pursuing or has been overtaken.
Move the pair to
rejected/with the reason. A proposal whose PR merged is not obsolete; move it toimplemented/and rewrite its plan into the present tense. - Rejected, keep: the losing idea remains a tempting, meaningful mistake and the note explains why it loses.
- Rejected, delete: the idea is obsolete, superseded or no longer plausible.
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 · -3 lines 7039a9a85ab4
- 4d ago First seen · 115 lines · 73 tokens per session scan A 83cfdf6b2936
archive-agent-notes is a skill published in the GitHub repository LodyAI/Lody (1,640 stars, last pushed today), licensed Apache-2.0. It adds 73 tokens to every session and 1,309 once invoked, about $0.0003 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-29.
Other skills, from other repositories
crewai-multi-agent
Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…
agent-state-bar
A design guide for an agent status bar: a short, automatically updated summary of progress, remaining tasks, tool counts, errors, and system state placed near the latest model input.
knowledge-org
A guide to organising large bodies of knowledge so an AI system can navigate relationships, summaries, and layers instead of searching only flat text chunks. It covers tree indexes, knowledge graphs, file-like structures, incremental updates, and long-term memory layouts.
memory-system
A guide to giving an AI agent persistent, user-specific memory across conversations. It covers what to remember, how to store it, how to update or compress it, and when to use memory instead of a shared knowledge base.
context-compression
A guide to shortening the information an agent carries between steps. It explains how to replace large tool outputs and old conversation details with compact, useful summaries while preserving important decisions and constraints.
llm-wiki
Build, ingest, query, and lint a persistent Markdown knowledge base using the Karpathy LLM Wiki pattern. Use for adding sources, maintaining interlinked wiki pages, answering from the knowledge base, filing durable research, or checking contradictions and index health. Do not use it to persist ordinary chat or…