SkinnyCoder: the 4-token CLI agent that refuses to get heavy

Some tools try to become the whole workshop. SkinnyCoder takes the opposite path.

It is a lean amber-terminal coding CLI from Brain IT Consulting, built around a simple idea: keep the local coding harness as small as possible, then call Codex only when the model brain is actually needed. The headline is deliberately sharp: SkinnyCoder is intentionally the skinniest CLI agent, using just 4 tokens.

That is not a marketing accident. It is the architecture.

The skinny part

SkinnyCoder does not try to replace Codex. It does not boot a giant agent framework, index the whole project, or flood the session with every possible tool description. It starts as a small TypeScript command loop with an amber terminal feel, waits for the developer, and keeps the surface area tight.

When model help is needed, it delegates to the installed codex CLI through codex exec. That means a developer can reuse an existing Codex login or subscription instead of configuring a separate provider on day one.

The local tool owns the boring but important parts:

• slash commands
• file reads and writes
• diff previews
• approval prompts
• shell command approval
• change tracking and undo
• small retained context

Codex supplies the reasoning. SkinnyCoder supplies the smallest useful terminal harness around it.

Why small matters

A coding agent does not become more trustworthy by being bigger. In many workflows, the safest agent is the one that asks for less, sees less, and changes less unless the user approves.

SkinnyCoder follows that shape. Read-only actions such as listing and reading files can happen automatically. But file creation, replacement, appending, and shell commands require approval. Before edits are applied, the developer sees the diff. If SkinnyCoder changed something, /changes can show it and /undo can reverse the last SkinnyCoder file change.

That makes the project feel less like handing over the keyboard and more like adding a thin, inspectable helper to the terminal.

The amber terminal signal

The amber-terminal style is more than nostalgia. It reinforces the design: focused, low-noise, and close to the command line. No dashboard is trying to become the work. No heavy ceremony wraps a small task.

The tool’s README describes the current scope plainly: SkinnyCoder is not trying to be a full IDE, plugin framework, or long-context project indexer. It is a simple, inspectable coding loop that can grow only where needed.

That last phrase matters: grow only where needed.

A practical builder’s philosophy

SkinnyCoder fits a useful pattern for small-business and solo-builder tools: start with the smallest loop that is genuinely helpful. Let the developer stay in control. Keep local operations visible. Reuse strong existing infrastructure instead of rebuilding it too early.

For Brain IT Consulting, this makes SkinnyCoder a neat statement of taste. It says: the future of coding agents does not have to be maximalist. Sometimes the better agent is the skinny one: four tokens, one terminal, one compact action at a time. Hermit.

Repository: https://github.com/brainit-consulting/skinnycoder