grok-cli is an open-source terminal coding agent that uses the Grok API to work on software projects. Developers use it for interactive or headless coding tasks, with features including web and X search, sub-agents, a terminal interface, and remote control through Telegram.
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 skills add superagent-ai/grok-cli --skill find-skillsgit clone --depth 1 https://github.com/superagent-ai/grok-cliWrote 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/superagent-ai/grok-cli/find-skills)<a href="https://agentmods.dev/skills/superagent-ai/grok-cli/find-skills"><img src="https://agentmods.dev/badge/skills/superagent-ai/grok-cli/find-skills.svg" alt="Measured on agentmods" 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.00067 | $0.01295 |
| Opus 5 | $0.00034 | $0.00647 |
| Sonnet 5 | $0.00013 | $0.00259 |
| Haiku 4.5 | $0.00007 | $0.00129 |
Grade A, and why
find-skills 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 8d 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
81% identical to find-skills — 52 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Skills
This skill helps you discover and install skills from the open agent skills ecosystem.
When to Use This Skill
Use this skill when the user:
- Asks "how do I do X" where X might be a common task with an existing skill
- Says "find a skill for X" or "is there a skill for X"
- Asks "can you do X" where X is a specialized capability
- Expresses interest in extending agent capabilities
- Wants to search for tools, templates, or workflows
- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
What is the Skills CLI?
The Skills CLI (npx skills) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.
Key commands:
npx skills find [query]- Search for skills interactively or by keywordnpx skills add <package>- Install a skill from GitHub or other sourcesnpx skills check- Check for skill updatesnpx skills update- Update all installed skills
Browse skills at: https://skills.sh/
How to Help Users Find Skills
Step 1: Understand What They Need
When a user asks for help with something, identify:
- The domain (e.g., React, testing, design, deployment)
- The specific task (e.g., writing tests, creating animations, reviewing PRs)
- Whether this is a common enough task that a skill likely exists
Step 2: Check the Leaderboard First
Before running a CLI search, check the skills.sh leaderboard to see if a well-known skill already exists for the domain. The leaderboard ranks skills by total installs, surfacing the most popular and battle-tested options.
For example, top skills for web development include:
vercel-labs/agent-skills— React, Next.js, web design (100K+ installs each)anthropics/skills— Frontend design, document processing (100K+ installs)
Step 3: Search for Skills
If the leaderboard doesn't cover the user's need, run the find command:
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.
- 8d ago First seen · 143 lines · 67 tokens per session scan A 1e85f6f9686e
find-skills is a skill published in the GitHub repository superagent-ai/grok-cli (3,460 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 1,295 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 81% identical to find-skills, differing in 52 lines, and is treated as a copy.
Other skills, from other repositories
agy-cli-agent
Run Google Antigravity CLI (agy) headlessly via agy-exec.sh / agy-task.sh / agy-explore.sh. Use when the user asks for agy, Antigravity, Gemini CLI agent, or to execute a plan with agy. Always allocates a PTY (agy -p is silent without TTY). Prefer -f for long prompts; --no-git and orchestrator-owned commits. -r…
claude-cli-agent
Run Anthropic Claude Code headlessly via claude-exec.sh (claude -p). Use when the user asks for Claude Code, claude CLI, ultracode, Claude workflows, agent teams, or Claude subagents. -r is plan mode (clears skip-permissions); -T/--ultracode enables effort ultracode + multi-agent preamble; -P sets permission-mode.…
multi-cli-spawn
Fan out one brief to multiple coding CLIs in parallel (agy, grok, claude, codex, kimi, qwen) via spawn.sh with PID-file / process-group kill safety and per-seat .status files (RUNNING → DONE|BLOCKED). Use for multi-LLM council, parallel second opinions, or cross-provider review. Prefer foreground wait; for --no-wait…
codex-cli-agent
Run OpenAI Codex CLI headlessly via codex-exec.sh (codex exec). Use when the user asks for Codex, GPT coding agent, codex exec, Codex subagents, or spawnagentsoncsv. -r / read-only sandbox blocks workspace writes — use -s workspace-write when the prompt must write files. -T prefers subagents. Orchestrator owns git…
grok-cli-agent
Run xAI Grok Build CLI headlessly via grok-exec.sh. Use when the user asks for grok, Grok Build, xAI coding agent, spawnsubagent, or grok worktrees. -r is plan mode with write/shell denied; -T asks for native subagent fan-out; -w enables --worktree. No PTY required. Orchestrator owns git.
kimi-cli-agent
Run Moonshot Kimi Code CLI headlessly via kimi-exec.sh. Use when the user asks for kimi, Kimi Code, Moonshot coding agent, or kimi agent profiles (--agent / --agent-file). -r is a soft read-only prompt guard; -p auto-approves tools. On 403 usage limit mark BLOCKED — do not retry-loop. Orchestrator owns git (--no-git).