Borrowing it
Nothing to install: this file belongs to lossless-claude/lcm. 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/lossless-claude/lcm/main/.agents/skills/lcm-release/SKILL.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/skills/lossless-claude/lcm/lcm-release)<a href="https://agentmods.dev/skills/lossless-claude/lcm/lcm-release"><img src="https://agentmods.dev/badge/skills/lossless-claude/lcm/lcm-release/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/lossless-claude/lcm/lcm-release"><img src="https://agentmods.dev/badge/skills/lossless-claude/lcm/lcm-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.00910 |
| Opus 5 | $0.00028 | $0.00455 |
| Sonnet 5 | $0.00011 | $0.00182 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
lcm-release 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lcm-release
Cut a versioned release of lossless-claude/lcm. This is a public npm package — never delete or overwrite existing git tags.
Note on release flow: This script is the canonical release process for this repo. It replaces any earlier Changesets-based or
version-pr.ymlautomation.WORKFLOW.mdandRELEASING.mdreflect the old flow and have not yet been updated.
Normal flow — use the script
Run .claude/skills/lcm-release/scripts/release.sh from the repo root:
bash .claude/skills/lcm-release/scripts/release.sh <version>
# e.g.
bash .claude/skills/lcm-release/scripts/release.sh 0.4.2
Resuming after a failure — pass --from-step N to skip already-completed steps:
bash .claude/skills/lcm-release/scripts/release.sh 0.4.2 --from-step 8 # re-watch publish.yml
bash .claude/skills/lcm-release/scripts/release.sh 0.4.2 --from-step 9 # just run develop sync
Sync develop standalone — when Step 9 needs to run independently:
bash .claude/skills/lcm-release/scripts/sync-develop.sh 0.4.2
The script handles everything end-to-end:
| Step | What it does |
|---|---|
| 0 | Checkout develop, pull, verify clean, sync develop←main (via PR if needed) |
| 1 | Guard: abort if tag or npm version already exists |
| 2 | Create release/vX.Y.Z branch from develop |
| 3 | Bump all 3 version files, verify they all match |
| 4 | Commit and push |
| 5 | Open PR targeting main |
| 6 | Wait for CI (skips gracefully if no CI configured) |
| 7 | Merge with --merge (preserves commit SHA on main) |
| 8 | Wait for publish.yml to complete |
| 9 | Open sync PR to bring the release commit back into develop; merge with --merge (preserves merge commit SHA) |
Prerequisites
- All feature PRs for this release are merged into
develop ghCLI is authenticated- You have a version number that is higher than any existing tag/npm release
Key invariants
- Never delete tags on a public package — if a version is taken, pick a higher one
- Release PRs target
main— the only exception to "PRs target develop" - Use
--merge(not squash) so the version bump SHA is preserved on main - All 3 version files must match:
package.json,.claude-plugin/plugin.json,.claude-plugin/marketplace.json- Note: marketplace.json stores version at
.plugins[0].version, not root
- Note: marketplace.json stores version at
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 80 lines · 56 tokens per session scan A e21e0f6f4477
lcm-release is a skill published in the GitHub repository lossless-claude/lcm (26 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 910 once invoked, about $0.0003 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 skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.