Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add lossless-claude/lcm/plugin install 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/commands/lossless-claude/lcm/lcm-diagnose)<a href="https://agentmods.dev/commands/lossless-claude/lcm/lcm-diagnose"><img src="https://agentmods.dev/badge/commands/lossless-claude/lcm/lcm-diagnose/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/commands/lossless-claude/lcm/lcm-diagnose"><img src="https://agentmods.dev/badge/commands/lossless-claude/lcm/lcm-diagnose.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.00027 | $0.00247 |
| Opus 5 | $0.00014 | $0.00123 |
| Sonnet 5 | $0.00005 | $0.00049 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
lcm-diagnose 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 9d 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.
What it actually says
/lcm-diagnose
Inspect recent Claude Code transcripts for historical lcm issues.
Instructions
Run lcm diagnose via Bash and display the output verbatim. If lcm is not on PATH (marketplace install), use node "${CLAUDE_PLUGIN_ROOT}/lcm.mjs" diagnose instead.
If the user asks for a wider scan, use:
lcm diagnose --alllcm diagnose --all --days 30lcm diagnose --verboselcm diagnose --json
After showing the results, suggest the next troubleshooting step:
lcm doctorfor current install healthlcm importif sessions were missed and need recovery
When to use
- After seeing hook errors in a Claude Code session
- When investigating missing sessions or gaps in ingestion
- During troubleshooting:
lcm doctorfor current state,lcm diagnosefor history,lcm importfor recovery
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.
- 9d ago First seen · 30 lines · 27 tokens per session scan A dbf890ddc894
lcm-diagnose is a command published in the GitHub repository lossless-claude/lcm (26 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 247 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.