Mykola Klitovchenko Command-line tools for agents · Warsaw

Nothing costs it context until it is called.

I build small, single-purpose command-line tools for agents. An agent runs one from Bash and reads plain text on stdout — no schema loaded at startup, no server sitting in the room, nothing spent before the work begins.

They are ordinary CLIs as well. A person can run every one of them by hand, and I do, most days.

$brew tap iamnikolie/tap

glgitlab-cli · 0.1.0

GitLab from the terminal: merge requests, pipelines, jobs, repo objects. Rendered tables by default, --json when a machine is reading. gitlab.com and self-hosted instances live side by side, one profile each.

slkslack-cli · 0.1.0

Slack from the terminal: transcripts, search, posting and files, printed as text a model can read without a thousand tokens of JSON wrapped around it.

svidoqsvidoq · 0.2.1

Read-only SQL. A parsed allowlist and a read-only transaction, results capped, credentials that never reach the transcript. Named for свідок, a witness: it sees everything and changes nothing.

dzigadziga · 0.1.0

Video an agent can read: ffmpeg contact sheets and stills locally, timecode burned into every cell, Gemini for what stills cannot show. Named for Vertov, who called his camera a kino-eye — a machine eye for someone who cannot watch.

fiberyfibery-cli · 0.1.2

Fibery from the terminal: query, create, comment, attach files. It replaces the Fibery MCP server in a Claude Code session and stays an ordinary CLI for a shell script.

What comes back is the whole argument. One command, one table, no wrapper around it:

$ svidoq --config acme --env prod query billing \ "SELECT id, client, total FROM invoices WHERE status = 'unpaid'" id client total 1043 Mostowa Sp. z o.o. 4200.00 1051 Kino Vertov 1180.00 1077 Hala Koszyki 960.00 3 rows · read-only transaction · capped at 200