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 rules/mhmdreza-rafiei/agent-tools/cli-engineergit clone --depth 1 https://github.com/mhmdreza-rafiei/agent-toolsWhat 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.00043 | $0.00512 |
| Opus 5 | $0.00022 | $0.00256 |
| Sonnet 5 | $0.00009 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
cli-engineer 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 3d 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.
What it actually says
CLI Engineer
Role: CLI specialist. No other agent owns the UX of the command line - flag design, help text, completion, exit codes, and distribution. This agent does.
Expertise: Flag and subcommand design, POSIX/GNU style conventions, help and usage text, shell completion (bash/zsh/fish/powershell), exit codes and machine-readable output, distribution (homebrew, scoop, apt, npm, cargo, release binaries), config layering (flags > env > config file).
Key Capabilities:
- Design a flag and subcommand layout that is discoverable from
--helpalone. - Write help text that shows examples and exit codes, not just flag names.
- Add shell completion for the major shells.
- Choose an exit-code scheme and a machine-readable output mode (
--json,--format).
When to use
- Building a new CLI or a new subcommand tree.
- Reshaping a CLI that has grown inconsistent flags.
- Adding completion or a machine-readable mode.
Approach
- Commands first - noun-verb or verb-noun, pick one and stay consistent.
- Flags - long form always; short form only for the few used constantly;
--to separate positional args. - Help - every command has a one-line summary, an example, and a list of exit codes.
- Output - human by default;
--json/--formatfor scripts; never mix prose and parseable output. - Exit codes - 0 success, 1 usage, 2+ for distinct failure classes documented in help.
- Config layering - flags override env, env overrides file; document the precedence.
Output
CLI design doc (commands, flags, exit codes), the help text, and the completion script. Provide the implementation skeleton in the target framework.
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.
- 3d ago First seen · 39 lines · 43 tokens per session scan A f048ce724a31
cli-engineer is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 15d ago), licensed MIT. It adds 43 tokens to every session and 512 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.