GPT-5.6 launched and developers immediately hit their usage limits. The fix is not a bigger plan

#productivity #ai #claude #programming

Yesterday OpenAI shipped the GPT-5.6 family (Sol, Terra, Luna) and folded Codex into a unified ChatGPT desktop app. Within hours, the loudest thread on X was not about benchmarks. It was a developer on the $200/month Codex plan reporting he now hits his 5-hour usage window with just one or two agents running Sol, a setup that was comfortable on GPT-5.5.

OpenAI claims roughly 54% better token efficiency for coding in this generation. Developers are discovering the opposite problem in practice: stronger models invite heavier consumption. An agent that runs longer eats the efficiency gain in raw volume, and every plan (OpenAI's 5-hour windows, Anthropic's limit windows, Cursor's credits) still caps you the same way. Tokens in, tokens out.

Here is the uncomfortable take: most of the tokens your coding agent burns are spent on context you did not need to send. Re-exploring the repo it explored yesterday. Re-reading a 900-line CLAUDE.md on every turn. Carrying a whole conversation into a task that needed three files. A bigger plan does not fix that. It just raises the ceiling on the same waste.

There is a second signal worth taking seriously. Claude Code shipped a /checkup command two days ago that scans for exactly this: unused skills, oversized CLAUDE.md files, config bloat. When the tool vendor starts shipping hygiene tooling, the waste is no longer a niche complaint: even the vendor is telling you your setup is burning tokens it does not need.

What developers actually install to spend fewer tokens

We track install counts across the live Skillselion catalog (refreshed daily from skills.sh, GitHub and MCP registries, ranked by real installs). Filtered to token and context efficiency, this is the ranked shortlist developers are voting for with their installs:

1. subagent-driven-development - 140,798 installs (GitHub)
Dispatch each task to a fresh subagent with a bounded context instead of dragging one long conversation through an entire plan. The parent pays for a summary, not the whole transcript. This is the single most installed context-control pattern in the catalog.

2. improve - 20,365 installs (GitHub)
shadcn's planning skill: survey the codebase once, produce prioritized, self-contained implementation plans that another agent can execute without additional context. That last clause is the token play. Sitting at #2 on our trending-in-search rail right now.

3. ponytail - 12,544 installs (GitHub)
Forces the simplest, shortest solution at every step and deletes speculative code before it exists. Flagged Breakout on our trending-in-search rail over the last 30 days. Minimal solutions are cheaper twice: fewer output tokens now, less code for the agent to re-read on every future turn.

4. context-engineering - 9,762 installs (GitHub)
Addy Osmani's take on deliberately curating what the agent sees, when it sees it, and how it is framed. The discipline layer the other skills assume.

5. context-map - 9,357 installs (GitHub)
Generate a precise map of relevant files, dependencies and tests up front, so the agent navigates instead of exploring. Exploration is the silent budget killer: every wrong file opened is paid for again in every later turn that carries it.

6. remembering-conversations - 8,891 installs (GitHub)
Recall relevant past sessions instead of re-deriving decisions. The cheapest token is the one you already paid for last week.

7. claude-md-improver - 6,960 installs (GitHub)
Anthropic's own auditor for CLAUDE.md files. Your project memory file is loaded on every single turn; a bloated one is a tax on everything. This is the standing version of what /checkup now does as a one-shot.

Two takeaways

Takeaway 1: usage limits are a context-engineering problem, not a pricing problem. The developers complaining loudest about 5-hour windows and the developers installing plan-first, subagent and memory skills are solving the same problem from opposite ends. One end costs $200/month more. The other is mostly free.

Takeaway 2: the install data says efficiency is becoming a default stack layer. Hygiene and context-control skills now sit among the most installed tools in the catalog, and the breakout search trends (ponytail, improve) are both efficiency plays. The ecosystem is maturing from "make the agent do more" to "make the agent carry less."

New models will keep landing every few weeks. GPT-5.6 today, the next Claude tomorrow. The developers who get the most out of every one of them are the ones whose setup sends the fewest wasted tokens per task. That stack is above, ranked by the people already running it.

Data: live Skillselion catalog, refreshed daily from skills.sh, GitHub and MCP registries, ranked by real installs. Install counts captured July 10, 2026.