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 adeotek/claude-code --skill load-contextgit clone --depth 1 https://github.com/adeotek/claude-codeWrote 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/adeotek/claude-code/load-context)<a href="https://agentmods.dev/skills/adeotek/claude-code/load-context"><img src="https://agentmods.dev/badge/skills/adeotek/claude-code/load-context/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/adeotek/claude-code/load-context"><img src="https://agentmods.dev/badge/skills/adeotek/claude-code/load-context.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.00106 | $0.00498 |
| Opus 5.5 | $0.00042 | $0.00199 |
| Sonnet 5.5 | $0.00021 | $0.00100 |
| Haiku 4.5 | $0.00011 | $0.00050 |
Grade A, and why
load-context 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 2mo 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
Load Context
Load a previously saved context from .memory/<name>.md in the current working directory and actively re-establish it in the conversation.
Steps
-
Extract the name from the user's prompt using the same kebab-case normalization as save-context (e.g., "auth work" →
auth-work). -
If no name was given, list available contexts and ask the user which to load:
ls .memory/*.md 2>/dev/nullPresent the names without the
.mdextension and without the.memory/path prefix. -
If the file doesn't exist (
.memory/<name>.mdnot found), list available contexts and suggest the closest match by name similarity. Do not fail silently. -
Read
.memory/<name>.mdusing the Read tool. -
Present the loaded context in two parts:
- Display the full file content so the user can scan it
- Follow with a brief conversational restatement of the current state and next steps, so the context is immediately active without requiring the user to re-read the file
Presentation Pattern
After displaying the file, restate the key points in 2–3 sentences:
Loaded auth-work (saved 2026-04-21). We were implementing JWT authentication middleware — the core logic in
middleware.tsis done and tests pass. The remaining work is creating the PR and adding an integration test.
Tailor this summary to what's most immediately actionable — prioritize Current State and Next Steps from the file. If the file has a Notes section with blockers or caveats, mention those too.
This positions the conversation to continue naturally. The user should be able to say "ok, let's do the next step" without needing to explain anything further.
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.
- 2mo ago First seen · 37 lines · 106 tokens per session scan A 531be23e2f85
load-context is a skill published in the GitHub repository adeotek/claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 106 tokens to every session and 498 once invoked, about $0.0004 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.
load-context compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| load-contextadeotek/claude-code | Skill | 2 | 6mo ago | MIT | A | 106 | Claude Code |
| knowledge-ingestopenclaw/openclaw | Skill | 394k | today | MIT | A | 80 | Claude Code, Codex |
| mem0-oss-to-platformmem0ai/mem0 | Skill | 69k | yesterday | Apache-2.0 | A | 217 | Claude Code, Codex |
| forgetasgeirtj/system_prompts_leaks | Skill | 71k | yesterday | CC0-1.0 | A | 0 | Claude Code, Codex |
| Cortexdanielmiessler/LifeOS | Skill | 20k | 2d ago | MIT | A | 184 | Claude Code |
| ha-data-storesshiwenwen/hope-agent | Skill | 1.9k | today | MIT | A | 115 | Claude Code, Codex |
| memoryopensquilla/opensquilla | Skill | 7.1k | 7d ago | Apache-2.0 | A | 44 | Claude Code, Codex |