openrouter-context-optimization
Optimize context window usage for OpenRouter models to reduce cost and improve quality. Use when hitting context limits, managing long conversations, or building RAG systems. Triggers: ''openrouter context'', ''context window'', ''openrouter token limit'', ''reduce tokens openrouter''. '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill openrouter-context-optimization --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# OpenRouter Context Optimization ## Overview OpenRouter models have varying context windows (4K to 1M+ tokens). Since pricing is per-token, stuffing unnecessary context wastes money and can degrade output quality. This skill covers context window lookup, token estimation, conversation trimming, chunking strategies, and Anthropic prompt caching for large contexts. ## Prerequisites - An OpenRouter
What does the openrouter-context-optimization skill do?
Optimize context window usage for OpenRouter models to reduce cost and improve quality. Use when hitting context limits, managing long conversations, or building RAG systems. Triggers: ''openrouter context'', ''context window'', ''openrouter token limit'', ''reduce tokens openrouter''. '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill openrouter-context-optimization --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
