rugged-gemini: Skill for Gemini CLI

.gemini/skills/cli-development/SKILL.md

cli-development is a skill for Gemini CLI from irahardianto/rugged-gemini. It costs 25 tokens per session (719 once invoked), scanned A, a copy of cli-development, MIT.

Guidance for designing command-line tools, programs operated through a terminal by typing commands, options, and arguments.

In plain words
What is it for?
Use it when planning command hierarchies, parsing arguments, adding prompts or shell completion, defining exit codes, or preparing a CLI for distribution.
Why use it?
It helps make commands understandable, scriptable, fast to start, and usable across different operating systems.

Skill for Gemini CLI

Written for Gemini CLI: installed under .gemini/. Also seen: mentions Gemini CLI.

This is irahardianto/rugged-gemini's own configuration. It tells Gemini CLI how to work on rugged-gemini itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything rugged-gemini configures →

Reuse

Borrowing it

Nothing to install: this file belongs to irahardianto/rugged-gemini. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/irahardianto/rugged-gemini/main/.gemini/skills/cli-development/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/irahardianto/rugged-gemini

Made for: Gemini CLI.

Wrote 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.

agentmods badge for cli-development

README.md
[![agentmods](https://agentmods.dev/badge/skills/irahardianto/rugged-gemini/cli-development/github.svg)](https://agentmods.dev/skills/irahardianto/rugged-gemini/cli-development)
Your own site
<a href="https://agentmods.dev/skills/irahardianto/rugged-gemini/cli-development"><img src="https://agentmods.dev/badge/skills/irahardianto/rugged-gemini/cli-development/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.

agentmods 80×15 button for cli-development

Your own site · 80×15
<a href="https://agentmods.dev/skills/irahardianto/rugged-gemini/cli-development"><img src="https://agentmods.dev/badge/skills/irahardianto/rugged-gemini/cli-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 719 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 89% copy Near-identical to another mod 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.1 $0.00025 $0.00719
Opus 5.5 $0.00010 $0.00288
Sonnet 5.5 $0.00005 $0.00144
Haiku 4.5 $0.00003 $0.00072

Measured 1mo ago against content hash fdab9b66500f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cli-development 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.

Origin

This is a copy

89% identical to cli-development — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.gemini/skills/cli-development/SKILL.md · 90 lines

How it starts

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

CLI Development Principles

Guidelines for building fast, intuitive, cross-platform CLI tools.

When to Invoke

  • Designing CLI tool architecture
  • Implementing command hierarchies and argument parsing
  • Adding shell completions and interactive features
  • Cross-platform distribution planning

Architecture

Command Hierarchy

app <command> [subcommand] [flags] [args]
app task create --priority high "Deploy fix"
app task list --status active --format json

Design Principles

  1. Startup time < 100ms — lazy-load expensive dependencies.
  2. Sensible defaults — zero-config for common cases.
  3. Progressive disclosure — simple interface, advanced flags for power users.
  4. Machine-readable output — --format json for scripting.
  5. Exit codes — 0 = success, 1 = error, 2 = usage error.

Argument Parsing Libraries

Language Library Notes
Go cobra + pflag Most popular, auto-completions
Rust clap (derive) Type-safe, auto-help
Python click or typer Decorator-based, typer for type hints
Node.js commander or yargs Mature, well-documented

Error Handling

  1. Helpful error messages — what went wrong, why, how to fix:

    Error: config file not found at ~/.myapp/config.yaml
    Hint: run 'myapp init' to create a default config
    
  2. --verbose / --debug flags for diagnostic output.

  3. Never show stack traces by default — only with --debug.

Shell Completions

Generate completions for bash, zsh, fish, PowerShell. Most CLI frameworks support this.

# Generate completions
myapp completion bash > /etc/bash_completion.d/myapp
myapp completion zsh > ~/.zsh/completions/_myapp

Cross-Platform

  1. Path handling — use filepath.Join (Go), Path (Python), not string concat.
  2. Line endings — handle \r\n on Windows.
  3. Color support — detect terminal capabilities, respect NO_COLOR env var.
  4. Unicode — test with non-ASCII filenames and input.

Read the full file on GitHub · 90 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. 1mo ago First seen · 90 lines · 25 tokens per session scan A fdab9b66500f

Subscribe to this mod's changes

cli-development is a skill published in the GitHub repository irahardianto/rugged-gemini (5 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 719 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to cli-development, differing in 6 lines, and is treated as a copy.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens