Lossless Claw is an OpenClaw plugin that preserves complete conversation history while keeping the active context within an AI model’s token limit. It stores messages in SQLite and builds linked summaries that agents can search and expand, with the catalogue providing skills and an instruction for its workflow.
Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/martian-engineering/lossless-claw/land-pr)<a href="https://agentmods.dev/skills/martian-engineering/lossless-claw/land-pr"><img src="https://agentmods.dev/badge/skills/martian-engineering/lossless-claw/land-pr/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/martian-engineering/lossless-claw/land-pr"><img src="https://agentmods.dev/badge/skills/martian-engineering/lossless-claw/land-pr.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.00042 | $0.01190 |
| Opus 5 | $0.00021 | $0.00595 |
| Sonnet 5 | $0.00008 | $0.00238 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade A, and why
land-pr 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 10d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lossless PR Landing
Use this skill when landing a lossless-claw pull request or answering whether it is ready to merge.
Workflow
-
Read repository instructions first.
- Follow
AGENTS.md, especially data-preservation, changeset, compatibility, and command-reporting rules. - If a deterministic merge wrapper exists for this repo, prefer it. Otherwise use the manual fallback below.
- Follow
-
Identify and pin the PR head.
- Fetch the real PR metadata:
gh pr view <PR> --json number,title,state,isDraft,baseRefName,headRefName,headRefOid,mergeable,mergeStateStatus,reviewDecision,statusCheckRollup,author,files,closingIssuesReferences,url - Treat
headRefOidas the merge pin. Re-read it immediately before merge.
- Fetch the real PR metadata:
-
Verify readiness.
- PR must be open, non-draft, mergeable, and clean.
- All required/current checks must be complete and successful on the pinned head:
gh pr checks <PR> --json name,state,bucket,workflow,link,startedAt,completedAt - If checks are pending, failing, missing, or tied to a different head SHA, do not merge.
- If the PR changes package-visible behavior, user-facing behavior, docs-visible behavior, compatibility metadata, config surface, or release behavior, answer the changeset question before merge.
- Do not expect external contributors to add Changesets metadata. Maintainers own it.
-
Run or confirm final review.
- Prefer the repo's actual PR base:
head=$(gh pr view <PR> --json headRefOid --jq .headRefOid) base=$(gh pr view <PR> --json baseRefName --jq .baseRefName) gh pr checkout <PR> test "$(git rev-parse HEAD)" = "$head" /Users/phaedrus/Projects/prompts/skills/autoreview/scripts/autoreview --mode branch --base "origin/$base" - Run branch review only from a checkout whose
HEADexactly matches the pinned PRheadRefOid. - Verify every accepted finding against the code before acting on it.
- Do not merge with unresolved actionable findings.
- Prefer the repo's actual PR base:
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.
- 10d ago First seen · 101 lines · 42 tokens per session scan A a9b5e035016d
land-pr is a skill published in the GitHub repository Martian-Engineering/lossless-claw (4,895 stars, last pushed 8d ago), licensed MIT. It adds 42 tokens to every session and 1,190 once invoked, about $0.0002 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
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.