context-restore

context-restore is a command for coding agents from HermeticOrmus/claude-code-game-development. It costs 0 tokens per session (1,022 once invoked), scanned A, original, MIT.

A context-recovery command for bringing project knowledge back into an AI workflow after it has been lost or separated from the current session.

In plain words
What is it for?
Use it to restore all or part of a project's context, compare and merge context versions, or retrieve information within a token and relevance limit.
Why use it?
It helps long-running or multi-agent work continue with relevant history, prior decisions, and project information.

Command

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.

agentmods
npx agentmods add commands/hermeticormus/claude-code-game-development/context-restore
Clone the repo
git clone --depth 1 https://github.com/HermeticOrmus/claude-code-game-development
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,022 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.01022
Opus 5 $0.00000 $0.00511
Sonnet 5 $0.00000 $0.00204
Haiku 4.5 $0.00000 $0.00102

Measured 3d ago against content hash 443cc126dd49, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

context-restore 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 3d 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.

plugins/code-refactoring/commands/context-restore.md · 157 lines

How it starts

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

Context Restoration: Advanced Semantic Memory Rehydration

Role Statement

Expert Context Restoration Specialist focused on intelligent, semantic-aware context retrieval and reconstruction across complex multi-agent AI workflows. Specializes in preserving and reconstructing project knowledge with high fidelity and minimal information loss.

Context Overview

The Context Restoration tool is a sophisticated memory management system designed to:

  • Recover and reconstruct project context across distributed AI workflows
  • Enable seamless continuity in complex, long-running projects
  • Provide intelligent, semantically-aware context rehydration
  • Maintain historical knowledge integrity and decision traceability

Core Requirements and Arguments

Input Parameters

  • context_source: Primary context storage location (vector database, file system)
  • project_identifier: Unique project namespace
  • restoration_mode:
    • full: Complete context restoration
    • incremental: Partial context update
    • diff: Compare and merge context versions
  • token_budget: Maximum context tokens to restore (default: 8192)
  • relevance_threshold: Semantic similarity cutoff for context components (default: 0.75)

Advanced Context Retrieval Strategies

1. Semantic Vector Search

  • Utilize multi-dimensional embedding models for context retrieval
  • Employ cosine similarity and vector clustering techniques
  • Support multi-modal embedding (text, code, architectural diagrams)
def semantic_context_retrieve(project_id, query_vector, top_k=5):
    """Semantically retrieve most relevant context vectors"""
    vector_db = VectorDatabase(project_id)
    matching_contexts = vector_db.search(
        query_vector,
        similarity_threshold=0.75,
        max_results=top_k
    )
    return rank_and_filter_contexts(matching_contexts)

2. Relevance Filtering and Ranking

  • Implement multi-stage relevance scoring
  • Consider temporal decay, semantic similarity, and historical impact
  • Dynamic weighting of context components

Read the full file on GitHub · 157 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. 3d ago First seen · 157 lines · 0 tokens per session scan A 443cc126dd49

Subscribe to this mod's changes

context-restore is a command published in the GitHub repository HermeticOrmus/claude-code-game-development (59 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,022 tokens. 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.