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.
npx agentmods add instructions/lossless-claude/lcm/agents-mdgit clone --depth 1 https://github.com/lossless-claude/lcmWrote 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/lossless-claude/lcm/agents-md)<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>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 | $0.02386 | $0.02386 |
| Opus 5 | $0.01193 | $0.01193 |
| Sonnet 5 | $0.00477 | $0.00477 |
| Haiku 4.5 | $0.00239 | $0.00239 |
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 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/*.mdfile 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 changesminor: new features or notable new behaviormajor: 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.
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.
- 5d ago First seen · 184 lines · 2,386 tokens per session scan C 4f37e517e772
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.
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.
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.
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).
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.
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 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).