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 skills add JesusGarcia9009/lethe-engineering --skill claude-codegit clone --depth 1 https://github.com/JesusGarcia9009/lethe-engineeringWrote 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/jesusgarcia9009/lethe-engineering/claude-code)<a href="https://agentmods.dev/skills/jesusgarcia9009/lethe-engineering/claude-code"><img src="https://agentmods.dev/badge/skills/jesusgarcia9009/lethe-engineering/claude-code/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/jesusgarcia9009/lethe-engineering/claude-code"><img src="https://agentmods.dev/badge/skills/jesusgarcia9009/lethe-engineering/claude-code.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.00032 | $0.00367 |
| Opus 5.5 | $0.00013 | $0.00147 |
| Sonnet 5.5 | $0.00006 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
lethe-offload 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 1mo 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
LETHE Offload
You have a LETHE MCP memory available. Use it to keep your context window small during long tasks, which saves tokens and preserves your attention for what matters.
The rule
When a tool result, file read, log, or API response is large (roughly > 1500 tokens) and you will not need all of it in the next step or two, archive it instead of keeping it:
- Call
lethe_archive(content=<the big text>, label=<short name>). - Keep only the returned handle (e.g.
handle=a3f9) in your reasoning. Drop the full text. - When you need it again, call
lethe_recall("a3f9")(by handle) orlethe_recall("<keywords>")(by content) to get it back.
When to archive
- ✅ Verbose file dumps you only needed to scan once.
- ✅ Long logs, stack traces, large JSON/API responses.
- ✅ Earlier step outputs that are "done" but might be referenced later.
When NOT to archive
- ❌ The current task instructions or active goal.
- ❌ Small outputs (under ~1500 tokens) — archiving them saves nothing.
- ❌ Anything you are about to use in the very next step.
Check your savings
Call lethe_status() to see how many items you have archived and how many tokens you have
offloaded so far. LETHE never deletes anything — archived content is always recoverable.
What ships with it
1 file 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.
- 1mo ago First seen · 37 lines · 32 tokens per session scan A 682eb613ccc3
lethe-offload is a skill published in the GitHub repository JesusGarcia9009/lethe-engineering (0 stars, last pushed 3mo ago), licensed Unlicense. It adds 32 tokens to every session and 367 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
fresh-start
Continue in a new chat without losing anything — writes a compact handoff to paste into a fresh conversation. Use whenever the user wants to move to a new chat or conversation, hits usage limits, says replies got slow or Claude forgets earlier details, or the conversation has grown long.
doc-digest
Turn a long document, PDF, transcript, spreadsheet or log into a compact working digest the conversation can continue from. Use when the user shares or pastes something long (several pages or more) and wants to discuss, analyze, compare or use it over more than one message, or asks to summarize a document so they can…
project-context
Turn background the user keeps re-explaining or re-pasting into reusable instructions, so new chats start with it for free. Use when the user repeats the same context, rules, style guide, persona or reference text across messages or chats, says they are tired of explaining the same thing, or asks how to set up a…
token-check
Estimate how many tokens a pasted text, an attached file or the conversation so far takes, what it means for the context window and usage limits, and how to cut it. Use when the user asks how big something is in tokens, why they keep hitting limits, or whether a file is too large to send.
history-trim
Analyze conversation history turn-by-turn and identify the exact point to run /clear from to prune stale history while keeping everything relevant to the current task. Use when history has grown long but you want to continue in the same session.
suggest-split
Detect when a conversation has drifted across multiple unrelated topics and recommend whether to start a new conversation. Identifies the optimal split point and summarizes what to carry forward. Use when a session has been running long or has covered many different tasks.