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 skills/hkuds/cli-anything/cli-anything-generatornpx skills add HKUDS/CLI-Anything --skill cli-anything-generatorgit 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/cli-anything-generator)<a href="https://agentmods.dev/skills/hkuds/cli-anything/cli-anything-generator"><img src="https://agentmods.dev/badge/skills/hkuds/cli-anything/cli-anything-generator.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 | $0.00104 | $0.00816 |
| Opus 5 | $0.00052 | $0.00408 |
| Sonnet 5 | $0.00021 | $0.00163 |
| Haiku 4.5 | $0.00010 | $0.00082 |
Grade A, and why
cli-anything-generator 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI-Anything Generator (Cursor Plugin Skill)
This skill is packaged inside the Cursor plugin as a supporting entry point. The primary generator UX is the plugin slash commands.
Prefer Slash Commands
| Goal | Command |
|---|---|
| Full 7-phase build | /cli-anything <path-or-repo> |
| Expand coverage | /cli-anything-refine <path> [focus] |
| Run tests | /cli-anything-test <path> |
| Validate checklist | /cli-anything-validate <path> |
| List tools | /cli-anything-list |
If the user speaks naturally ("build a CLI for ./gimp"), run the same workflow as the matching command.
Consumer Path (Separate)
This skill is not the Hub consumer. For finding/installing published CLIs:
npx skills add HKUDS/CLI-Anything --skill cli-hub-meta-skill -g -y
Per-app skills live under the repo skills/ tree and install via npx skills add.
PLUGIN_ROOT and Methodology
- Resolve
PLUGIN_ROOTvia discovery pointer then stamp:~/.cursor/cli-anything-generator.root/%USERPROFILE%\.cursor\cli-anything-generator.root{install}/PLUGIN_ROOT.txt- default
~/.cursor/plugins/local/cli-anythingifreferences/HARNESS.mdexists there
- Read
{PLUGIN_ROOT}/references/HARNESS.mdwith an absolute path. - Read the matching file under
{PLUGIN_ROOT}/references/commands/. - Use guides under
{PLUGIN_ROOT}/references/guides/on demand. - Helper scripts:
{PLUGIN_ROOT}/scripts/repl_skin.py,preview_bundle.py,skill_generator.py,templates/.
Path remapping (from HARNESS / plugin docs)
| Document reference | Installed plugin path |
|---|---|
guides/... |
references/guides/... |
cli-anything-plugin/repl_skin.py |
scripts/repl_skin.py |
cli-anything-plugin/preview_bundle.py |
scripts/preview_bundle.py |
cli-anything-plugin/skill_generator.py |
scripts/skill_generator.py |
templates/SKILL.md.template |
scripts/templates/SKILL.md.template |
docs/PREVIEW_PROTOCOL.md |
references/docs/PREVIEW_PROTOCOL.md |
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.
- 4d ago First seen · 85 lines · 104 tokens per session scan A f32e8c22451c
cli-anything-generator is a skill published in the GitHub repository HKUDS/CLI-Anything (48,809 stars, last pushed 13d ago), licensed Apache-2.0. It adds 104 tokens to every session and 816 once invoked, about $0.0005 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…