9arm's skills repo is small, but it has one cost idea worth stealing

I have reviewed four Claude Code skill repos so far, some with hundreds of thousands of stars. This one is different. 9arm, a Thai creator, has a repo of around 2,900 stars, far smaller, just 6 skills, and its bucket layout is borrowed straight from Matt Pocock's repo.

To be straight: on scale or fame, this repo isn't in the same league as the other four. But it has one skill sharp enough to be worth writing up, and it covers something the other four don't: controlling cost by choosing which model does which job. So this isn't a review of the whole set. It's taking the single most useful idea.

Part 1The sharp idea: send grunt work to a cheap model

The skill called qwen-agent does one thing, and does it well. It splits work into two piles. The repetitive, low-thought work, renaming variables across a file, writing boilerplate, summarizing long logs, gets sent to a cheap model like Qwen instead. The more expensive main model is kept for the work that genuinely needs judgment.

What makes it hold up in practice is that it forces large jobs to be split into pieces that fit the cheap model's smaller context, rather than dumping the whole thing and hoping. There's a companion skill, qwenchance, that watches for the agent re-reading the same file in a loop, or thinking for a thousand words without acting, and makes it break or hand off, so tokens don't quietly burn.

Part 2Why it works: match the task's value to the tool's price

This lines up with a principle I hold anyway: don't push everything through the single most expensive model. Jobs aren't worth the same. Work that's easy to check and needs no interpretation should sit with the cheapest thing that can do it, a cheap model or plain code. Work that needs context or a judgment call is where you pay for the expensive model.

Think this way and cost follows the value of the work instead of being flat and high across everything. And it doesn't cost you quality, because the work that needs a strong model still gets one. You just stop melting the expensive one on jobs a cheap tool handles fine.

Part 3Straight talk about the repo, and how to use it

About the repo itself, plainly: it's small and personal, 6 skills, and the bucket layout is borrowed from Matt Pocock's repo without attribution. So its value isn't in taking the whole thing, it's in this one cost idea, which matches the lesson from the whole series: no repo is meant to be swallowed whole, just take the good part.

You don't even need Qwen to use it. The move is to look at the repetitive work you do every day and ask which of it doesn't need an expensive model. Renaming, reformatting, summarizing, hand those to something cheaper, and the bill eases off without the work getting worse.

This post is one layer in the 7-layer architecture of a production AI agent.