rescue-tokens

Detect and mitigate token waste causing rate limit errors during AI coding sessions.

4|Updated May 20, 2026
One-click install
npx skills add https://github.com/valorisa/Claude-Skills --skill rescue-tokens
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rescue-tokens
Source: https://github.com/valorisa/Claude-Skills/tree/main/skills/rescue-tokens
Command: npx skills add https://github.com/valorisa/Claude-Skills --skill rescue-tokens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses silent token waste that leads to unexpected rate limit errors during AI coding sessions, where long conversations, incorrect model choices, verbose output, and unnecessary full-file processing burn through context capacity without warning. Most assistants waste additional tokens explaining how to save tokens instead of acting immediately under pressure, worsening the problem right when resource conservation is critical.

Core Features & Use Cases

  • Auto-activation on emergency red flags: Triggers immediately when any one of 7 symptoms is present (rate limit warnings, 40%+ context usage, 5+ loaded MCP plugins, Opus used for simple tasks, etc.) using OR logic so no multiple symptoms are required to act.
  • Immediate, permission-free corrective actions: Follows a pre-defined action matrix to compact context, switch to appropriate models, disable unused MCPs, request text excerpts instead of full file ingestion, and refuse inefficient sub-agent usage without asking for confirmation.
  • Strict terse response rules: Enforces under-100-word responses under pressure, eliminating markdown sections, reasoning blocks, tables, and unnecessary justifications that waste tokens.
  • Use case example: If you are running a CRUD refactor with Opus and hit a rate limit, the skill immediately switches you to Sonnet and begins work without lengthy justification, saving thousands of tokens.

Quick Start

Mention that you are receiving rate limit warnings or ask Claude to complete a task without losing context to activate the skill's automatic emergency token-saving workflow.

Frequently Asked Questions about rescue-tokens

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

FAQPage Schema
How do I stop unexpected rate limit errors caused by token waste in Claude Code?

To stop unexpected rate limit errors from token waste, an automated emergency response can compact context, switch models, and enforce strict response length limits without needing manual intervention.

Why does using Opus for simple implementation tasks cause rate limit warnings?

Using Opus for simple implementation tasks causes rate limit warnings because it rapidly consumes context window capacity through verbose outputs and heavy processing, wasting thousands of tokens unnecessarily.

What is the best way to reduce token consumption during long AI coding sessions?

The best way to reduce token consumption during long AI coding sessions is enforcing under-100-word responses, disabling unused MCP plugins, and requesting text excerpts instead of full file ingestion for PDFs and images.

Can I automatically switch from Opus to Sonnet when hitting a context window limit?

Yes, you can automatically switch from Opus to Sonnet when hitting a context window limit. The system detects rate limit red flags and immediately switches models to preserve context capacity without asking for confirmation.

Does loading multiple MCP plugins increase token waste during AI coding?

Yes, loading multiple MCP plugins increases token waste during AI coding. Having 5 or more loaded plugins serves as an auto-activation trigger, prompting immediate corrective actions to disable unused plugins and conserve context.

When should I avoid full ingestion of expensive file types like PDFs and images?

You should avoid full ingestion of expensive file types like PDFs and images during rate limit emergencies, instead requesting text excerpts to preserve context window capacity and prevent silent token waste.