cli-enhance

A command that adds common usability features to existing Rust command-line programs, such as colored output, progress bars, prompts, completion suggestions, configuration, logging, and clearer errors.

In plain words
What is it for?
Use it to add selected improvements, such as colors, progress indicators, interactive questions, shell completions, better errors, configuration handling, or logging.
Why use it?
It avoids having to design and add these user-interface and support features one by one. The additions can make terminal programs easier to understand and use.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/geoffjay/claude-plugins/cli-enhance
Clone the repo
git clone --depth 1 https://github.com/geoffjay/claude-plugins
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,818 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.03818
Opus 5 $0.00012 $0.01909
Sonnet 5 $0.00005 $0.00764
Haiku 4.5 $0.00002 $0.00382

Measured 2d ago against content hash 8bf15d00ef83, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cli-enhance scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/rust-cli-developer/commands/cli-enhance.md · 675 lines

How it starts

The opening of the file, as written. The whole thing — 675 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLI Enhance Command

Add modern CLI features to an existing Rust CLI application, including colors, progress bars, interactive prompts, shell completions, and beautiful error messages.

Arguments

  • $1 - Feature to add: "colors", "progress", "prompts", "completions", "errors", "config", "logging", or "all" (required)
  • $2 - Path to project directory (optional, defaults to current directory)

Usage

# Add all enhancements
/cli-enhance all

# Add specific feature
/cli-enhance colors
/cli-enhance progress
/cli-enhance completions

# Enhance specific project
/cli-enhance colors /path/to/my-cli

Available Enhancements

1. Colors and Styling

Add semantic colors to CLI output using owo-colors.

What Gets Added:

  • Dependency: owo-colors
  • Dependency: supports-color (for detection)
  • Color module with semantic helpers
  • NO_COLOR environment variable support
  • Terminal capability detection

Example Implementation:

// src/colors.rs
use owo_colors::{OwoColorize, Stream};

pub fn success(message: &str) {
    println!(
        "{} {}",
        "✓".if_supports_color(Stream::Stdout, |text| text.green().bold()),
        message
    );
}

pub fn error(message: &str) {
    eprintln!(
        "{} {}",
        "✗".if_supports_color(Stream::Stderr, |text| text.red().bold()),
        message
    );
}

pub fn warning(message: &str) {
    println!(
        "{} {}",
        "⚠".if_supports_color(Stream::Stdout, |text| text.yellow().bold()),
        message
    );
}

pub fn info(message: &str) {
    println!(
        "{} {}",
        "ℹ".if_supports_color(Stream::Stdout, |text| text.blue().bold()),
        message
    );
}

pub fn supports_color() -> bool {
    use supports_color::Stream as ColorStream;
    supports_color::on(ColorStream::Stdout).is_some()
}

Usage in Code:

use crate::colors;

colors::success("Build completed!");
colors::error("Failed to read file");
colors::warning("Configuration incomplete");
colors::info("Processing 10 files");

Read the full file on GitHub · 675 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 675 lines · 24 tokens per session scan A 8bf15d00ef83

Subscribe to this mod's changes

cli-enhance is a command published in the GitHub repository geoffjay/claude-plugins (8 stars, last pushed 10mo ago), licensed MIT. It adds 24 tokens to every session and 3,818 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.