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 egorfedorov/claude-context-optimizer --skill doc-digestgit clone --depth 1 https://github.com/egorfedorov/claude-context-optimizerWrote 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/egorfedorov/claude-context-optimizer/doc-digest)<a href="https://agentmods.dev/skills/egorfedorov/claude-context-optimizer/doc-digest"><img src="https://agentmods.dev/badge/skills/egorfedorov/claude-context-optimizer/doc-digest/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/egorfedorov/claude-context-optimizer/doc-digest"><img src="https://agentmods.dev/badge/skills/egorfedorov/claude-context-optimizer/doc-digest.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.00075 | $0.00581 |
| Opus 5.5 | $0.00030 | $0.00232 |
| Sonnet 5.5 | $0.00015 | $0.00116 |
| Haiku 4.5 | $0.00007 | $0.00058 |
Grade A, and why
doc-digest 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 today.
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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document digest
A long attachment is re-sent with every later message of the conversation. A digest that keeps what the work needs lets the rest of the work run on a fraction of it, most of all in a fresh conversation that starts from the digest instead of the file.
Write the digest
In the user's language, inside one code block so it copies cleanly, at most about a tenth of the source and never more than 800 words:
- What it is: title, author or source, date, length, purpose, in one or two lines.
- Map: the sections or parts in order, one line each, with page, slide, sheet or timestamp references, so a later question can go straight to the right place.
- Key content: the claims, decisions, requirements, figures and definitions the user is likely to need, each with its reference. Quote exact wording only where it matters: legal terms, numbers, names, error messages.
- Gaps and doubts: what the document leaves open, contradicts or gets wrong, in a line each.
Fit the digest to what the user said they want to do with the document: a contract review keeps obligations, dates and penalties; a dataset keeps the columns, units and odd values; a log keeps the first error and what led to it. Never pad it with general background.
Then
Give the size in one line, as an estimate: "The document is about 40K tokens; the digest is about 1.5K." Then offer one of these, whichever fits:
- Keep going here and answer from the digest, opening the original only for a detail the digest lacks.
- Continue in a new conversation: open it, paste the digest and the
question. Every later message then costs a few percent of what it does
here. Offer the
fresh-starthandoff if there is more than the document to carry over. - In a Project (claude.ai): add the original to the Project's knowledge and the digest to its instructions, so new chats in it start with both.
Don't claim the digest replaces the document for anything legal, financial or safety-critical; point to the original sections for those.
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.
- today First seen · 52 lines · 75 tokens per session scan A 840d78123993
doc-digest is a skill published in the GitHub repository egorfedorov/claude-context-optimizer (116 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 581 once invoked, about $0.0003 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-10-18.
Other skills, from other repositories
md-to-pdf
Convert Markdown to PDF via reportlab or weasyprint engines. Triggers - pdf, md to pdf, markdown to pdf, generate pdf.
alive:save
The human wants to checkpoint. Or: the stash has grown heavy — 5+ items, 30+ minutes, a natural pause in the work. The squirrel doesn't decide when to save. It surfaces the need and lets the human pull the trigger. Runs the full save protocol: confirms stash, writes log, updates state, generates projections…
alive:capture-context
Use when external content arrives in the session — emails, transcripts, screenshots, documents, files, or in-session research worth keeping. Also use when there's nothing obvious to capture — the skill checks 03Inbox/ for unrouted files and enters inbox scan mode. Stores raw content, routes to bundles, extracts tasks…
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:load-context
The human mentions a walnut to work on, asks about a specific venture/experiment/project, or wants to check status — not just explicit 'load X'. Load the brief pack (3 files), resolve the people involved, check the active bundle — then surface one observation and ask what to work on. Context loads in tiers: walnut and…
alive:mine-for-context
Deep context extraction from source material. Creates reference bundles, builds extraction plans, tracks what's been extracted, and discovers new targets — people, subjects, patterns, connections. The archaeologist that turns raw sources into structured knowledge. Can be invoked by alive:session-history for targeted…