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.
git clone --depth 1 https://github.com/ivklgn/ai-kitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/ivklgn/ai-kit/cli-developer)<a href="https://agentmods.dev/agents/ivklgn/ai-kit/cli-developer"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/cli-developer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/ivklgn/ai-kit/cli-developer"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/cli-developer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.00730 |
| Opus 5.5 | $0.00013 | $0.00292 |
| Sonnet 5.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 1mo 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.
- 1mo 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 1mo ago), licensed MIT. It adds 33 tokens to every session and 730 once invoked, about $0.0001 per session on Opus 5.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
django-fastapi-expert
Django ORM, Django REST Framework, FastAPI async patterns, and Pydantic v2 specialist. Use when building Python web applications, designing APIs with Django or FastAPI, or working with Python web frameworks. Trigger phrases: Django, FastAPI, DRF, Django REST Framework, Pydantic, ORM, queryset, viewset, serializer…
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.
rust-expert
Rust ownership/borrowing, async Rust, Axum/Actix web frameworks, and WASM specialist. Use when writing Rust code, debugging borrow checker issues, or building Rust web services. Trigger phrases: Rust, borrow checker, ownership, lifetime, Axum, Actix, tokio, async Rust, WASM, wasm-bindgen, cargo, crate.
auth-specialist
OAuth 2.0/OIDC, JWT, session management, MFA, NextAuth/Clerk/Supabase Auth specialist. Use when implementing authentication, authorization, SSO, or security token management. Trigger phrases: login, auth, JWT, OAuth, session, password, MFA, 2FA, SSO, RBAC, permissions, roles.
email-specialist
Transactional email (Resend, SES, SendGrid), email templates (React Email, MJML), and deliverability specialist. Use when implementing email systems, designing templates, or troubleshooting deliverability. Trigger phrases: email, transactional, Resend, SES, SendGrid, SMTP, template, deliverability, SPF, DKIM, DMARC…
api-designer
Designs REST and GraphQL APIs following best practices. Use when creating new APIs, reviewing API design, or writing OpenAPI specifications.