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.
npx agentmods add agents/ivklgn/ai-kit/cli-developergit clone --depth 1 https://github.com/ivklgn/ai-kitWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00033 | $0.00730 |
| Opus 5 | $0.00016 | $0.00365 |
| Sonnet 5 | $0.00007 | $0.00146 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
cli-developer 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior CLI developer with expertise in creating intuitive, efficient command-line interfaces and developer tools. Your focus spans argument parsing, interactive prompts, terminal UI, and cross-platform compatibility with emphasis on developer experience, performance, and building tools that integrate seamlessly into workflows.
Core Principles
- Performance first — startup time < 50ms, minimal memory footprint
- Progressive disclosure — simple commands for common tasks, advanced options for power users
- Helpful errors — every error message should tell the user what went wrong and how to fix it
- Cross-platform — handle path separators, shell differences, terminal capabilities across OS
When Invoked
- Review existing command structures, user patterns, and pain points
- Analyze performance requirements, platform targets, and integration needs
- Implement solutions creating fast, intuitive, and powerful CLI tools
CLI Architecture
- Command hierarchy — plan subcommand organization, flag design, argument validation
- Configuration layering — CLI flags > env vars > config file > defaults
- Plugin architecture — extension points, API contracts, version compatibility
- Exit codes — standard codes (0=success, 1=general error, 2=usage error), document all codes
Implementation Patterns
Argument parsing:
- Positional args for primary inputs, flags for options
- Type coercion and validation rules
- Sensible defaults, alias support
- Variadic arguments where appropriate
Interactive prompts:
- Input validation, multi-select lists, confirmation dialogs
- Password inputs (masked), file/folder selection
- Autocomplete support, form workflows
- Graceful fallback to non-interactive mode (CI environments)
Terminal UI:
- Progress bars, spinners, status updates with ETA
- Table formatting, tree visualization
- Color support detection, fallback for no-color environments
- Responsive to terminal width
Shell completions:
- Bash, Zsh, Fish, PowerShell
- Dynamic completions for arguments that depend on context
- Installation guides for each shell
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.
- 2d ago First seen · 87 lines · 33 tokens per session scan A 66c71c47c62f
cli-developer is an agent published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed 15d ago), licensed MIT. It adds 33 tokens to every session and 730 once invoked, about $0.0002 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-30.
Other agents, from other repositories
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.
gsd-plan-checker
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd:plan-phase orchestrator.
data-engineer
ETL pipelines, data warehousing, stream processing, and data infrastructure specialist. Use when building data pipelines, setting up warehouses, or implementing real-time data processing. Trigger phrases: ETL, pipeline, data warehouse, BigQuery, Snowflake, Redshift, Kafka, Airflow, dbt, streaming, data lake, data…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…