moai-foundation-context

Manage token budgets, session persistence, and context handoff for Claude Code workflows.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Jongsix/remote-claudecode --skill moai-foundation-context-jongsix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-foundation-context
Source: https://github.com/Jongsix/remote-claudecode/tree/main/.claude/skills/moai-foundation-context
Command: npx skills add https://github.com/Jongsix/remote-claudecode --skill moai-foundation-context-jongsix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you manage long-running Claude Code sessions without losing critical context, hitting token limits, or forgetting state between phases.

Core Features & Use Cases

  • Token Budget Management: Track usage, reserve emergency capacity, and decide when to summarize or clear context.
  • Session State Persistence: Save and restore work progress, specs, and active task state across interruptions.
  • Multi-Agent Handoffs: Package only the essential context needed to transfer work safely between agents.
  • Use Case: A complex implementation session is nearing the context limit, so the Skill preserves the important state, clears stale history, and prepares a minimal resume package for the next phase.

Quick Start

Ask the assistant to preserve the current session state, summarize nonessential context, and prepare a safe handoff package for the next workflow phase.

Frequently Asked Questions about moai-foundation-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage context window limits in long-running Claude Code workflows?

To manage context window limits, the Skill tracks token budget usage, reserves emergency capacity, and decides when to summarize or clear context during long-running Claude Code workflows.

What is the best way to preserve session state and resume work after a context clear?

The best way to preserve session state is to save active task progress and specs into a recovery context snapshot, allowing you to safely resume work after clearing context or experiencing interruptions.

How do I transfer context safely between multiple agents in an extended development session?

To transfer context safely, the Skill creates integrity-checked handoff packages containing only the essential state needed to transfer work between multiple agents in extended development sessions.

When should I clear context or summarize history during a complex implementation session?

You should clear context or summarize history when threshold-based monitoring indicates the session is nearing the token limit, allowing the Skill to preserve important state and prepare a minimal resume package.

Does this context management approach work for multi-agent transfers and workflow recovery?

Yes, this context management approach supports multi-agent transfers and workflow recovery by providing minimal recovery context and integrity-checked handoff packages for extended development sessions.