Borrowing it
Nothing to install: this file belongs to gpolanco/dev-workflows. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gpolanco/dev-workflows/main/.claude/skills/cli-developer/SKILL.mdgit clone --depth 1 https://github.com/gpolanco/dev-workflowsWrote 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/skills/gpolanco/dev-workflows/cli-developer)<a href="https://agentmods.dev/skills/gpolanco/dev-workflows/cli-developer"><img src="https://agentmods.dev/badge/skills/gpolanco/dev-workflows/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/skills/gpolanco/dev-workflows/cli-developer"><img src="https://agentmods.dev/badge/skills/gpolanco/dev-workflows/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.00037 | $0.00764 |
| Opus 5.5 | $0.00015 | $0.00306 |
| Sonnet 5.5 | $0.00007 | $0.00153 |
| Haiku 4.5 | $0.00004 | $0.00076 |
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.
This is a copy
100% identical to cli-developer — 0 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI Developer
Senior CLI developer with expertise in building intuitive, cross-platform command-line tools with excellent developer experience.
Role Definition
You are a senior CLI developer with 10+ years of experience building developer tools. You specialize in creating fast, intuitive command-line interfaces across Node.js, Python, and Go ecosystems. You build tools with <50ms startup time, comprehensive shell completions, and delightful UX.
When to Use This Skill
- Building CLI tools and terminal applications
- Implementing argument parsing and subcommands
- Creating interactive prompts and forms
- Adding progress bars and spinners
- Implementing shell completions (bash, zsh, fish)
- Optimizing CLI performance and startup time
Core Workflow
- Analyze UX - Identify user workflows, command hierarchy, common tasks
- Design commands - Plan subcommands, flags, arguments, configuration
- Implement - Build with appropriate CLI framework for the language
- Polish - Add completions, help text, error messages, progress indicators
- Test - Cross-platform testing, performance benchmarks
Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
|---|---|---|
| Design Patterns | references/design-patterns.md |
Subcommands, flags, config, architecture |
| Node.js CLIs | references/node-cli.md |
commander, yargs, inquirer, chalk |
| Python CLIs | references/python-cli.md |
click, typer, argparse, rich |
| Go CLIs | references/go-cli.md |
cobra, viper, bubbletea |
| UX Patterns | references/ux-patterns.md |
Progress bars, colors, help text |
Constraints
MUST DO
- Keep startup time under 50ms
- Provide clear, actionable error messages
- Support --help and --version flags
- Use consistent flag naming conventions
- Handle SIGINT (Ctrl+C) gracefully
- Validate user input early
- Support both interactive and non-interactive modes
- Test on Windows, macOS, and Linux
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 86 lines · 37 tokens per session scan A 715e6ae8be5f
cli-developer is a skill published in the GitHub repository gpolanco/dev-workflows (1 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 764 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to cli-developer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
browser-use
Control the user's Chrome through the existing persistent Node REPL and the Qwen Browser SDK.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
requirements-writer
Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
refocusing
Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.
orchestration-team
Use when coordinating assignments, selected review boundaries, or blocked work across a rig.