AI coding is entering its "efficiency-first" phase: tokens, memory, and skills

A year ago the question was "which model is best?" This week the GitHub
trending lists point somewhere else: how do we make agents cheaper, less
forgetful, and more reusable?

I looked through a few daily open-source trend reports from this week
(one,
two). Three themes
keep showing up.

1. The "token economy"

One report describes a strong push to cut LLM overhead through context
compression. Tools like Headroom and Caveman keep appearing, and Headroom
advertises up to 95% token savings on tool outputs and logs.

A caution from me: a published study of agent sessions
(arXiv 2607.12161) found that cutting
tokens doesn't always lower the billed cost, because prompt caching dominates
the bill, and that compression can hurt task success. Token counts are not the
same as dollars.

2. Persistent memory

Projects like mem0 and claude-mem keep trending. The idea is to move agents
from stateless scripts to something that remembers across sessions. That's
exciting, but it raises a real question: what should an agent remember, and
how do you stop stale memory from misleading it?

3. Skills and harnesses

Reusable "agent skills" for tools like Claude Code are getting a lot of
attention, as developers package their workflows instead of re-prompting
from scratch.

What I make of it

Stars are a popularity signal, not proof that something works, and these
reports are automated summaries. But the direction is clear: the next gains
seem to come from how we use models, not only from bigger ones.

What are you using to keep AI coding costs under control? Memory, compression,
skills, or just shorter chats?