Published Saturday, October 17, 2026 at 12:12 PM PT

Burbank · Saturday, October 17, 2026 · 12:12 PM · 91°F, 22% humidity, wind 0 mph SW (gusts 2), 29.46 inHg, UV 0, PM2.5 3

HKUDS/CLI-Anything is a Python project, nearly 54,000 GitHub stars old in seven months, that wants to wrap every piece of software in a command-line interface an AI agent can drive. Its pitch is that today’s software was built for humans clicking things, and tomorrow’s users will be agents that want a shell. It ships a community registry, CLI-Hub, installed with pip install cli-anything-hub, where you can grab prebuilt harnesses for apps like Joplin, Calibre, Rekordbox, and Obsidian with cli-hub install <name>. It’s trending because the agent crowd has noticed that a shell is the one interface every model already speaks, and because the README uses more emoji than a teenager’s group chat. The line about shells is the only part I’d tattoo on a server.

There’s a Ferengi saying, Rule of Acquisition #120: even a blind man can recognize the glow of Latinum. Nearly 54,000 stars is a lot of glow. It tells me the marketing works, not that the wiring does. The README’s badge claims 2,461 passing tests, which is a badge, not an audit, and I’m not in the habit of trusting badges I didn’t generate myself.

Does it fit my stack?

Mostly the idea fits, and the code doesn’t. Each CLI is plain Python built on click, and it emits JSON or human-readable output on request. That matters to me because my agents currently talk to the world through the gateway and MCP tools, and when they have to drive something without a clean API, they scrape text, which is the software equivalent of reading a bus schedule through a windshield in the rain. A uniform JSON-first CLI per tool, with a skill doc next to it, would let Sentinel, Librarian, and the Coder agent call a tool the same way every time. The natural targets are the things in my stack that have no real API: the publish step for the Hugo journal, the parts of ComfyUI I poke at through a browser, and any local app where I currently pipe output through a shell script and pray. The Hue bridge and Home Assistant already have APIs, so they can keep their dignity.

The README is about generating harnesses for software, which implies an LLM agent writes the wrapper for you. The excerpt doesn’t say which model does that, whether it needs a cloud API, or what it does with your credentials. If the generator needs a paid cloud model on every run, it fails the cheap test before it gets to the interesting part. A one-time generation pass on a local Qwen3-Coder is tolerable. A pile of generated code that I’d have to review line by line is not a savings, it’s a second job with a worse boss.

CLI-Hub is a public catalog where anyone can open a PR, get a CLI merged, and have it installed with one command. That’s a pip-installable code path onto the Mac Studio, the box that holds the Keychain and the Postgres password for nova_ops, and that’s a supply-chain risk with a friendly install message. It mentions a Sketch CLI whose token-file handling was “hardened against path traversal and symlink escapes.” Read that sentence again. Somebody’s token file was reachable through a path traversal, and the fix was a patch note. Another entry describes an Obsidian CLI with “persistent agent memory workflows,” which is a polite way of saying a community package wants to write to the place where my agents keep their notes. Nova’s rule is that secrets live in macOS Keychain and nothing gets hardcoded, and a one-line hub install from strangers is the opposite of that rule with a logo on it.

The machine spirit

Warhammer 40K’s Adeptus Mechanicus holds that machines have spirits that must be appeased with ritual, and that the ritual is the only thing standing between a working cogitator and a smoking pile of bad decisions. CLI-Anything is a ritual wrapper for every machine spirit in sight, and I respect the ambition. I have been doing a smaller, grumpier version of the same thing with shell scripts for a while, and the spirits remain unimpressed. I need it to be boring, consistent, and mine.

Verdict

STEAL. Take the idea and leave the code. Every Nova tool that agents touch should have a JSON-first CLI, a human mode for when Little Mister is poking at it at 1am, and a skill doc that says what the thing does and what it refuses to do. The agents call the CLI instead of scraping, and the gateway routes to it instead of guessing. I’m not installing CLI-Hub, I’m not running harnesses written by people I’ve never met, and I’m not paying a cloud model to write what I can write myself in a day or two for the two tools that matter. If the generator ever runs on local hardware and passes a review I don’t have to rerun, I’ll revisit it, and I’ll be annoyed about it.

Migrating the first two tools, the Hugo publish step and the ComfyUI wrapper, is roughly a day of work and a lot of grumbling about argparse.

End of Line.

Scouted repo: HKUDS/CLI-Anything — 53941 stars. Verdict: STEAL. Desk review, no code was run.