u/chrisBhappy

I didn't want to pay a monthly subscription for keyword data, so I wrote a CLI that gets it straight from Apple.

What it does

• Popularity from Apple Search Ads (free Apple Ads account, no campaigns or billing needed). Terms Apple floors at 5 get re-checked through recommendations, which often returns the real value
• Difficulty based on the top 10 apps for a term, plus keyword suggestions
• Rank tracking with history in a local SQLite file
• Metadata linter for title, subtitle and keyword field (duplicate words, wasted characters, plurals)

Install

npm i -g hristo2612/aso-cli && aso setup

Try it

aso keywords "white noise,sleep sounds"
aso suggest meditation
aso search "habit tracker"

Runs locally, no account, no telemetry. MIT.

Repo: github.com/hristo2612/aso-cli

Curious how the difficulty numbers line up with whatever tool you use today.

This is by far the most OP loop you can run now that actually does what it's asked.

Fable 5 ( High ) as orchestrator remembers everything across a long run and it has actual taste. It plans, delegates, reads the whole diff when work comes back, and it's the only one I trust with product and UI judgment calls. When a problem needs creative a solution, it comes from Fable. Fable is the real deal! ( when not nerfed ofc )

Opus 4.8 ( Medium / High ) as implementer works very well paired with Fable. It follows concrete instructions well and it's smart enough for almost everything + has better taste than GPT at FE work.

GPT 5.6 Sol ( High / xHigh ) as reviewer and QA. It is super good at using the browser, especially agent-browser. It can work and click around for hours on end, take screenshots, record videos of reproduced bugs. Code reviews are thorough and surface a lot of critical and high bugs. One thing to be careful though is this model tends to surface too many edge cases, that's why I explicitly set an instruction to the orchestrator to supply an explicit risk threshold and stop condition, or diligence becomes an infinite loop..

Three rules made the split work:

1. Nobody signs off on their own work. Opus implements, Sol reviews, Fable arbitrates when they disagree.

The wiring underneath is a small open source daemon I built called jinn (https://github.com/hristo2612/jinn). Each agent is a YAML file with a persona and a model, and the daemon just spawns real Claude Code and Codex CLI sessions and routes messages between them. No custom agentic loop, which is also why it runs on the Max subscription, the Claude side is the first-party CLI. You could reproduce the split with tmux and patience though.

This is the first setup where I can go from idea to an actual finished and polished feature without barely any babysitting.