
Claude Better Cli
- 746 installs
- 66 repo stars
- Updated July 9, 2026
- aradotso/trending-skills
claude-better-cli is a Claude Code skill that installs a compatibility-first reimplementation of the Claude CLI with faster startup and lower memory while keeping drop-in command parity.
About
claude-better-cli is a performance-oriented CLI skill from aradotso/trending-skills for a compatibility-first reimplementation of the official Claude CLI called claude-better. It advertises up to 73% faster startup and up to 80% lower resident memory while preserving drop-in command compatibility for existing scripts and habits. Developers reach for claude-better-cli when terminal harnesses feel sluggish, CI agents spend time waiting on CLI boot, or memory pressure appears during repeated Claude invocations.
- Up to 73% faster startup times
- Up to 80% lower resident memory usage
- 100% command-level compatibility with original Claude CLI
- Zero migration cost for existing aliases and scripts
- 98.7% byte-for-byte output parity on tested commands
Claude Better Cli by the numbers
- 746 all-time installs (skills.sh)
- +7 installs in the week ending Jul 17, 2026 (Skillselion tracking)
- Ranked #1,351 of 16,659 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: CRITICAL risk (skills.sh audit)
- Data as of Jul 19, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aradotso/trending-skills --skill claude-better-cliAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 746 |
|---|---|
| repo stars | ★ 66 |
| Security audit | 0 / 3 scanners passed |
| Last updated | July 9, 2026 |
| Repository | aradotso/trending-skills ↗ |
How do you speed up the Claude CLI startup time?
Get a dramatically faster and lighter drop-in replacement for the official Claude CLI without changing any scripts or habits.
Who is it for?
Developers and automation authors who invoke Claude repeatedly from shell scripts, harnesses, or CI and need faster, lighter CLI startup.
Skip if: Teams locked to official Anthropic CLI support contracts or workflows that require unreleased official-only flags without compatibility guarantees.
When should I use this skill?
A developer complains about slow Claude CLI startup, high memory usage, or wants a drop-in faster replacement called claude-better.
What you get
Installed claude-better binary with drop-in CLI compatibility and faster invocation profile
- installed claude-better CLI binary
- faster-compatible claude command invocations
By the numbers
- Advertises up to 73% faster CLI startup
- Advertises up to 80% lower resident memory usage
Files
claude-better
Skill by ara.so — Daily 2026 Skills collection.
claude-better is a compatibility-first reimplementation of the Claude CLI focused on aggressive performance improvements: up to 73% faster startup and up to 80% lower resident memory, while maintaining 100% command-level compatibility with the original Claude CLI.
What It Does
- Faster cold starts:
--helpgoes from 182ms → 49ms;chatsession bootstrap from 311ms → 102ms - Lower memory: sustained interactive sessions drop from ~412MB → ~83MB RSS
- Drop-in compatible: 100% pass rate on primary command forms, 100% exit-code match, 98.7% byte-for-byte output parity
- Zero migration cost: existing scripts, aliases, and muscle memory continue to work unchanged
Availability
⚠️ Source code is provided for selected high-profile customers only and available upon request. Contact the maintainer at krzyzanowskim/claude-better for access.
If you have access, install as described in your onboarding materials. The binary is a drop-in replacement — substitute it wherever you invoke claude.
Installation (Once You Have Access)
# Typical binary drop-in replacement pattern
# Place the claude-better binary in your PATH before the original claude
export PATH="/path/to/claude-better/bin:$PATH"
# Verify it's being picked up
which claude
claude --version# Or alias it explicitly without touching PATH
alias claude='/path/to/claude-better/bin/claude-better'Key Commands
claude-better mirrors the Claude CLI surface exactly. All commands you know work as-is:
# Show help (cold start: ~49ms vs 182ms baseline)
claude --help
# Check auth status (warm start: ~58ms vs 146ms baseline)
claude auth status
# Start an interactive chat session (~102ms bootstrap vs 311ms baseline)
claude chat
# One-shot non-interactive command (~131ms vs 428ms baseline)
claude -p "Summarize this file" < input.txt
# All standard flags pass through unchanged
claude --model claude-opus-4-5 chat
claude --output-format json -p "List 3 facts about Rust"Configuration
claude-better reads the same configuration as the original Claude CLI. No new config format is required.
# Standard Claude CLI env vars are respected
export ANTHROPIC_API_KEY=$ANTHROPIC_API_KEY
# The tool reads ~/.claude/ config directory as normal
# No migration of config files neededPerformance Characteristics
| Scenario | Baseline | claude-better | Improvement |
|---|---|---|---|
--help cold start | 182ms | 49ms | 73% faster |
auth status warm | 146ms | 58ms | 60% faster |
chat bootstrap | 311ms | 102ms | 67% faster |
| One-shot command | 428ms | 131ms | 69% faster |
| RSS after 30min session | 412MB | 83MB | 80% less |
| Streaming jitter p95 | 91ms | 24ms | 74% lower |
Scripting Patterns
Since compatibility is 100%, all existing scripting patterns work unchanged:
#!/usr/bin/env bash
# Existing Claude CLI scripts work without modification
# Non-interactive pipeline usage
echo "Explain this error:" | cat - error.log | claude -p /dev/stdin
# Exit code handling (100% compatible)
if claude auth status; then
echo "Authenticated"
else
echo "Not authenticated — run: claude auth login"
exit 1
fi
# JSON output parsing
claude --output-format json -p "What is 2+2?" | jq '.content'#!/usr/bin/env bash
# Long-lived interactive session — memory pressure is significantly reduced
# Useful on memory-constrained machines (laptops, CI runners)
claude chatCompatibility Notes
- CLI surface: 100% compatible with targeted Claude CLI command forms
- Exit codes: 100% match on documented exit-code behavior
- Output parity: 98.7% byte-for-byte; 100% semantic parity after whitespace/timestamp/terminal-width normalization
- Tested environments: macOS (Apple Silicon), Linux, containerized CI
- Tested against: 1,200 synthetic invocations, 87 flag combinations, 42 interactive flows, 14 failure-mode scenarios
Troubleshooting
Binary not found after install
# Ensure claude-better/bin is earlier in PATH than original claude
echo $PATH | tr ':' '\n' | grep -n claude
which claude # should point to claude-betterUnexpected output differences
# 1.3% of outputs differ before normalization (timestamps, whitespace, terminal width)
# If a script breaks on exact output matching, add normalization:
claude -p "..." | tr -s ' ' | sed 's/[[:space:]]*$//'Auth not recognized
# claude-better reads the same auth store as the original CLI
# If auth fails, re-authenticate via the standard flow:
claude auth loginFalling back to original CLI
# If you hit an edge case, unset the alias/PATH change to revert instantly
unalias claude
# or
export PATH="<original-path-without-claude-better>"Architecture Notes (For Contributors / Evaluators)
The performance gains come from specific implementation choices documented in the README:
- Zero-copy streaming pipeline for token output (reduces streaming jitter)
- Precomputed command registry instead of dynamic startup discovery (cuts cold-start time)
- Aggressively bounded allocation for session state (drives memory reduction)
- Lazy subsystem initialization — only the active command path pays startup cost
- Compatibility shim layer that preserves flags/behavior without carrying the full original stack
Related skills
How it compares
Pick claude-better-cli when terminal invocation latency or memory is the bottleneck rather than in-editor Cursor or IDE integrations.
FAQ
Is claude-better-cli compatible with existing Claude scripts?
claude-better-cli installs claude-better as a compatibility-first reimplementation designed for drop-in command parity with the official Claude CLI so existing scripts and habits keep working.
What performance gains does claude-better advertise?
claude-better-cli documents up to 73% faster startup and up to 80% lower resident memory compared with the official Claude CLI during typical terminal invocations.
Is Claude Better Cli safe to install?
skills.sh reports 0 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.