lcm AGENTS.md

lcm AGENTS.md is an instructions file for Codex, OpenCode from lossless-claude/lcm. It costs 2,386 tokens per session, scanned C, original, MIT.

Repository and release guidance for lcm, a TypeScript SQLite daemon that stores Claude session memories across context resets.

In plain words
What is it for?
It is for checking release notes, merging changes, rebuilding and testing the project, running its health check, and syncing the plugin cache.
Why use it?
It helps maintainers review changes, choose release versions, keep the local environment stable, and ensure updated plugins are picked up.

Instructions file for CodexOpenCode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/lossless-claude/lcm/agents-md
Clone the repo
git clone --depth 1 https://github.com/lossless-claude/lcm

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for lcm AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/lossless-claude/lcm/agents-md.svg)](https://agentmods.dev/instructions/lossless-claude/lcm/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/lossless-claude/lcm/agents-md"><img src="https://agentmods.dev/badge/instructions/lossless-claude/lcm/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,386 This file is loaded in full into every session.
When invoked 2,386 The same file — it is already loaded in full.
Security scan C 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.02386 $0.02386
Opus 5 $0.01193 $0.01193
Sonnet 5 $0.00477 $0.00477
Haiku 4.5 $0.00239 $0.00239

Measured 5d ago against content hash 4f37e517e772, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

lcm AGENTS.md scanned grade C with 2 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 5d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf "$CACHE" && mkdir -p "$CACHE"

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

### curl / wget — BLOCKED
AGENTS.md · 184 lines

How it starts

The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Instructions

See WORKFLOW.md for the full development workflow.

PR Review And Merge

  • Before merging a PR, check whether it changes user-facing behavior or should appear in npm release notes.
  • If yes, make sure a maintainer adds a .changeset/*.md file before merge or immediately after in a follow-up PR.
  • Do not expect external contributors to know or run the Changesets workflow.
  • Use the smallest appropriate bump:
    • patch: fixes, compatibility work, docs-visible behavior changes
    • minor: new features or notable new behavior
    • major: breaking changes
  • Treat a PR as not release-ready until the changeset question has been answered.

Local Environment Stability

After merging a feature PR, always rebuild and verify the local environment before moving on:

git checkout develop && git fetch origin develop && git reset --hard origin/develop
npm run build && chmod +x dist/bin/lcm.js && npm link
lcm doctor          # must show 0 failures
npm test            # must pass

Also sync the global plugin cache so Claude Code picks up updated hooks and commands:

# Find the cached plugin directory (version and owner may vary)
CACHE=$(ls -d ~/.claude/plugins/cache/*/lossless-claude/*/ 2>/dev/null | sort -V | tail -1)
if [ -n "$CACHE" ]; then
  rm -rf "$CACHE" && mkdir -p "$CACHE"
  cp .claude-plugin/plugin.json "$CACHE/"
  cp -r .claude-plugin/commands "$CACHE/"
  cp -r .claude-plugin/hooks "$CACHE/"
fi

Then run /reload-plugins inside Claude Code to apply the changes.

If anything fails, fix it before starting the next feature. A broken local env wastes time on every subsequent session (stale dist, wrong binary, hook errors, mismatched plugin cache).

Documentation Requirements

All changes that affect user-facing behavior must include complete documentation in the docs/ folder. This includes new features, configuration changes, CLI commands, hook additions, and API changes. Documentation should be written for end users, not developers — explain what it does, how to use it, and any configuration options.

Read the full file on GitHub · 184 lines

Changes

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.

  1. 5d ago First seen · 184 lines · 2,386 tokens per session scan C 4f37e517e772

Subscribe to this mod's changes

lcm AGENTS.md is an instructions file published in the GitHub repository lossless-claude/lcm (24 stars, last pushed yesterday), licensed MIT. It adds 2,386 tokens to every session, about $0.0119 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other instructions, from other repositories

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.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

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.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens