session-health-monitor

Monitors and compresses AI session tokens to prevent 413 context overflow errors.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/KodaTCG/openclaw-session-health-monitor-skill --skill session-health-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-health-monitor
Source: https://github.com/KodaTCG/openclaw-session-health-monitor-skill/tree/main
Command: npx skills add https://github.com/KodaTCG/openclaw-session-health-monitor-skill --skill session-health-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and templates (resource) components.

What problem does it solve?

This Skill prevents costly 413 context overflow errors by proactively monitoring token usage, compressing chat history, and intelligently routing tasks to sub-agents, especially optimized for Discord's high token burn rate.

Core Features & Use Cases

  • Proactive Token Monitoring: Automatically checks session token usage at regular intervals.
  • Intelligent Compression: Compresses chat history to memory files when token thresholds are approached, with new idempotent compression to prevent data loss.
  • Durable State Separation: Critical information like API keys and configurations are saved separately and never compressed.
  • Sub-Agent Routing: Offloads heavy computational tasks to sub-agents to save tokens.
  • Discord Optimization: Features aggressive thresholds and image blocking for Discord environments.
  • Use Case: Ensure your AI assistant remains responsive and avoids crashes during long, active Discord conversations by automatically managing token usage and compressing older messages.

Quick Start

Use the session-health-monitor skill to automatically manage your Discord session's token usage.

Frequently Asked Questions about session-health-monitor

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

FAQPage Schema
How do I prevent 413 context overflow errors during long AI chat sessions?

To prevent 413 context overflow errors, you can proactively monitor token usage and compress chat history. Automated threshold checks and sub-agent routing keep your session within limits without crashing.

What is the best way to manage Discord token burn rate for an AI assistant?

Managing Discord token burn rate requires aggressive token thresholds and image blocking. Automated monitoring tools can optimize your session by compressing older messages and offloading tasks to sub-agents.

How does chat history compression work without losing critical API keys or configurations?

Chat history compression safely preserves critical configurations through durable state separation. API keys and configurations are saved separately and never compressed, while only older chat messages are compressed.

Can I use sub-agent routing to save tokens during heavy computational tasks?

Yes, sub-agent routing saves tokens by offloading heavy computational tasks to sub-agents. This reduces the main session's token load and helps prevent context overflow errors.

Does session token monitoring support idempotent compression for data integrity?

Session token monitoring supports idempotent compression to ensure data integrity. This mechanism prevents data loss by ensuring that repeated compression operations yield the same result without duplicating data.

Why does my AI session crash during active Discord conversations and how do I fix it?

AI sessions crash during active Discord conversations due to exceeding token limits. Fix this by automatically managing token usage, blocking images, and compressing older messages when thresholds are approached.