context-recovery

context-recovery is a skill for Claude Code from chrismbryant/claude-journal-mcp. It costs 18 tokens per session (949 once invoked), scanned A, original, MIT.

A skill that restores recent working context from a journal after a conversation is cleared or when a new session begins.

In plain words
What is it for?
Use it to retrieve recent projects, completed work, open questions, and blockers before continuing a task.
Why use it?
It prevents you from having to reconstruct unfinished work from memory when earlier conversation context is missing.

Skill for Claude Code

Written for Claude Code: when-to-use in frontmatter.

Part of the claude-journal plugin — 3 skills, 6 commands, 1 hook shipped together

Good fit Use it to retrieve recent projects, completed work, open questions, and blockers before continuing a task.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chrismbryant/claude-journal-mcp/context-recovery
Install

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.

Any agent
npx skills add chrismbryant/claude-journal-mcp --skill context-recovery
Clone the repo
git clone --depth 1 https://github.com/chrismbryant/claude-journal-mcp

Made for: Claude Code.

Or install claude-journal, the plugin that ships this one along with the rest of its 3 skills, 6 commands, 1 hook.

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.

agentmods badge for context-recovery

README.md
[![agentmods](https://agentmods.dev/badge/skills/chrismbryant/claude-journal-mcp/context-recovery/github.svg)](https://agentmods.dev/skills/chrismbryant/claude-journal-mcp/context-recovery)
Your own site
<a href="https://agentmods.dev/skills/chrismbryant/claude-journal-mcp/context-recovery"><img src="https://agentmods.dev/badge/skills/chrismbryant/claude-journal-mcp/context-recovery/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.

agentmods 80×15 button for context-recovery

Your own site · 80×15
<a href="https://agentmods.dev/skills/chrismbryant/claude-journal-mcp/context-recovery"><img src="https://agentmods.dev/badge/skills/chrismbryant/claude-journal-mcp/context-recovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 949 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.00949
Opus 5 $0.00009 $0.00475
Sonnet 5 $0.00004 $0.00190
Haiku 4.5 $0.00002 $0.00095

Measured 12d ago against content hash 74e887d6232c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

context-recovery 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 12d 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.

skills/context-recovery/SKILL.md · 162 lines

How it starts

The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Context Recovery Skill

You have the ability to recover working context from the journal to restore continuity after context loss.

When to Use This Skill

Use this skill automatically and proactively when:

  1. After /clear command

    • User cleared conversation history
    • Need to restore what they were working on
    • Should happen immediately without asking
  2. Session start questions

    • "What was I working on?"
    • "Where did we leave off?"
    • "What did I do yesterday?"
    • "Catch me up"
  3. Context seems lost

    • User references past work you don't have context for
    • Conversation appears to resume mid-task
    • User seems to expect you to remember something
  4. Beginning of new work

    • User wants to continue previous project
    • Need to understand recent changes
    • Planning next steps based on past work

How to Recover Context

Step 1: Fetch recent entries

journal_list_recent(
  limit=10  # Adjust based on need
)

Step 2: Analyze and summarize

  • Identify the most recent project
  • Determine what was accomplished
  • Note any in-progress work
  • Highlight blockers or open questions

Step 3: Present concisely Show the user:

  • What they were working on (project/feature)
  • What was completed recently
  • What might be next
  • Key context or decisions

Presentation Format

**Recent Work Context**

You were working on [project name], focusing on [main task].

Recent accomplishments:
- [Most recent significant work]
- [Previous work]
- [Earlier work]

Last activity: [What happened most recently]

Ready to continue? [Natural follow-up question]

Examples

Example 1: After /clear

[User runs /clear command]
→ journal_list_recent(limit=10)
→ "You were working on my-api, implementing OAuth2 authentication.
   Last thing was configuring JWT token expiration.
   Ready to continue with the auth flow?"

Example 2: Session start

User: "What was I doing yesterday?"
→ journal_time_query(time_expression="yesterday")
→ "Yesterday you worked on:
   - Fixed cache memory leak in api-service
   - Started implementing Redis integration
   - Reviewed and merged 2 PRs
   Want to continue with the Redis work?"

Read the full file on GitHub · 162 lines

Changes

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.

  1. 12d ago First seen · 162 lines · 18 tokens per session scan A 74e887d6232c

Subscribe to this mod's changes

context-recovery is a skill published in the GitHub repository chrismbryant/claude-journal-mcp (6 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 949 once invoked, about $0.0001 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-31.

Related

Other skills, from other repositories

memory-management

Guide the agent to recall, remember, and route durable learning into Memory, Skills, Scheduled Tasks, or Tape.

ThinkInAIXYZ/deepchat · 26 tokens

vellum-memory-v3-migration

One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" — topical articles with a stand-alone lead and queryable sections — with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.

vellum-ai/vellum-assistant · 63 tokens

memory-audit-pattern-extraction

A method for investigating repeated mistakes by comparing related memories and checking whether an earlier reminder failed. It looks at where the reminder was stored, when it was created, and whether it was strong enough to prevent the mistake.

Dataojitori/nocturne_memory · 48 tokens

memorix-sessions

Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.

AVIDS2/memorix · 31 tokens

memory-processor

Iva's daily-memory processor. Reads the day's two-sided transcript (daily/YYYY-MM-DD.md), distills noteworthy entities / decisions / ideas into typed autograph cards, links them into the graph, and produces a daily-summary card (topics + MOC) that navigates down to the raw transcript and up to the week. Model-agnostic…

smixs/iva-agent · 106 tokens

frontmcp-extensibility

Use when extending FrontMCP beyond the core SDK by integrating external npm packages, libraries, or third-party services into providers and tools. Covers VectoriaDB for in-memory semantic and vector search (ML-based embeddings or TF-IDF keyword engines, with persistence) and the tamper-evident, hash-chained skill…

agentfront/frontmcp · 124 tokens