CLI-Anything turns software and services into command-line interfaces that AI agents can use to perform tasks and produce artifacts. It is intended for people building or using agent workflows with tools such as coding assistants, design software, and other applications. The catalogue entries are skills, commands, a plugin, and a rule for working with CLI-Anything.
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 HKUDS/CLI-Anything --skill hermes-skillgit clone --depth 1 https://github.com/HKUDS/CLI-AnythingWrote 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/hkuds/cli-anything/hermes-skill)<a href="https://agentmods.dev/skills/hkuds/cli-anything/hermes-skill"><img src="https://agentmods.dev/badge/skills/hkuds/cli-anything/hermes-skill/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/hkuds/cli-anything/hermes-skill"><img src="https://agentmods.dev/badge/skills/hkuds/cli-anything/hermes-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.01017 |
| Opus 5.5 | $0.00021 | $0.00407 |
| Sonnet 5.5 | $0.00011 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
cli-anything-hermes 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cli-anything-hermes — 100% identical, 1 lines differ
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI-Anything for Hermes Agent
Use this skill when the user wants Hermes Agent to act like the CLI-Anything builder.
Before implementation, use the full methodology source of truth when available:
- If this skill is being used from inside the
CLI-Anythingrepository, read../cli-anything-plugin/HARNESS.mdfirst. - If that local file is unavailable, clone or download
cli-anything-pluginfromhttps://github.com/HKUDS/CLI-Anything/tree/main/cli-anything-plugin, then useHARNESS.mdand the resources around it from that folder. - Only if both local and network retrieval fail, follow the condensed rules below.
Inputs
Accept either:
- A local source path such as
./gimpor/path/to/software - A GitHub repository URL
Derive the software name from the local directory name after cloning if needed.
Hermes Tool Bindings
Hermes agents build harnesses by combining these built-in tools:
| Tool | Role in Harness Workflow |
|---|---|
terminal |
Run shell commands, install packages, execute CLI tools, run tests |
execute_code |
Generate and write Python files (Click CLI, backend modules, tests) |
delegate_task |
Parallelize analysis or generation subtasks |
read_file / write_file |
Read and write harness source files |
patch |
Make targeted edits to generated code |
Consult the Hermes Agent documentation for the exact tool invocation syntax.
Modes
Build
Use when the user wants a new harness.
Produce this structure:
<software>/
└── agent-harness/
├── <SOFTWARE>.md
├── setup.py
└── cli_anything/
└── <software>/
├── README.md
├── __init__.py
├── __main__.py
├── <software>_cli.py
├── core/
├── utils/
└── tests/
Implement a stateful Click CLI with:
- one-shot subcommands
- REPL mode as the default when no subcommand is given
--jsonmachine-readable output- session state with undo/redo where the target software supports it
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 · 133 lines · 53 tokens per session scan A 04579318cfae
cli-anything-hermes is a skill published in the GitHub repository HKUDS/CLI-Anything (53,078 stars, last pushed 24d ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,017 once invoked, about $0.0002 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 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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
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…