A Skill That Tells Your Agent to Write Less Code Is the Fastest-Rising Repo on GitHub

The largest available cost lever might not be the model. It might be a prompt telling the model to calm down.

DietrichGebert/ponytail is a portable agent skill with a simple thesis: force coding agents toward the minimal solution. YAGNI first. Standard library before custom code. Native platform features before dependencies. The persona it adopts is the laziest senior dev on the team, the one who responds to your 400-line abstraction with "why isn't this a dict."

The README reports benchmarks on real Claude Code sessions editing a FastAPI plus React repo: roughly 54% less code written, up to 94% in some cases, about 20% cheaper, about 27% faster than the same agent with no skill installed. Trending trackers put it around 76,000 to 80,000 stars with roughly 8,200 gained in seven days, the highest star velocity on GitHub as of July 7. It ships adapters for Cursor, Windsurf, Cline, Copilot Chat, Aider, Kiro, and Zed.

Those are self-reported numbers from a README. I want to be clear about that. Nobody has independently replicated them, the benchmark is one repo, and "54% less code" is trivially gameable if the code that got cut was code you needed. But the direction is right in a way I feel in my hands every day. Left alone, coding agents write too much. They add abstraction layers for a single caller. They write a config system for two constants. They install a dependency to parse a date. My most common Claude Code correction, by a wide margin, is some version of "delete half of that."

Put ponytail next to the Databricks story and you get the actual argument. Databricks attacked cost by choosing a cheaper model at equal quality: 34% saved. ponytail claims 20% cheaper and 27% faster by changing what the model is told to produce, model-agnostic. Same problem, different layer of the stack, and the two compose. Nobody's stopping you from running GLM 5.2 with a restraint policy.

The counter-argument is real: minimal code isn't automatically good code. My design background is why my engineering works, and craft sometimes costs lines. An abstraction with one caller today has two next month. But agents don't have taste about when that's true, and their default is to over-build. A blunt restraint policy corrects a blunt bias. It's the right shape of fix.

What to do: install it, run it on a branch, and diff. If your agent's output gets worse, you learned something about your codebase. If it gets shorter and the tests still pass, you just cut a fifth of your token bill with a markdown file. Scan it first, because a 1,900-skill installable registry with no provenance model now exists (see Hot Projects below) and skills execute in your environment.