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-cloudanalyzernpx skills add HKUDS/CLI-Anything --skill cli-anything-cloudanalyzergit clone --depth 1 https://github.com/HKUDS/CLI-AnythingWhat 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.00070 | $0.01801 |
| Opus 5 | $0.00035 | $0.00901 |
| Sonnet 5 | $0.00014 | $0.00360 |
| Haiku 4.5 | $0.00007 | $0.00180 |
Grade A, and why
cli-anything-cloudanalyzer 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.
How it starts
The opening of the file, as written. The whole thing — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cli-anything-cloudanalyzer
Agent-friendly command-line harness for CloudAnalyzer — a QA platform for mapping, localization, and perception point cloud outputs.
27 commands across 8 groups.
Installation
pip install cli-anything-cloudanalyzer
Prerequisites:
- Python 3.10+
- CloudAnalyzer:
pip install cloudanalyzer
Global Options
cli-anything-cloudanalyzer [--project FILE] [--json] COMMAND [ARGS]...
| Option | Description |
|---|---|
-p, --project TEXT |
Path to project JSON file |
--json |
Output results as JSON (for agent consumption) |
Command Groups
1. evaluate — Point Cloud Evaluation (6 commands)
evaluate run
Evaluate a point cloud against a reference (Chamfer, F1, AUC, Hausdorff).
cli-anything-cloudanalyzer evaluate run source.pcd reference.pcd
cli-anything-cloudanalyzer --json evaluate run source.pcd reference.pcd
Options: --plot TEXT, --threshold FLOAT
evaluate compare
Compare two point clouds with optional registration.
cli-anything-cloudanalyzer evaluate compare src.pcd tgt.pcd --register gicp
Options: --register TEXT (icp/gicp/none)
evaluate diff
Quick distance statistics between two point clouds.
cli-anything-cloudanalyzer evaluate diff a.pcd b.pcd --threshold 0.1
evaluate batch
Batch evaluation of multiple point clouds against a reference.
cli-anything-cloudanalyzer --json evaluate batch results/ reference.pcd --min-auc 0.95
Options: --min-auc FLOAT, --max-chamfer FLOAT
evaluate ground
Evaluate ground segmentation quality (precision, recall, F1, IoU).
cli-anything-cloudanalyzer --json evaluate ground est_ground.pcd est_ng.pcd ref_ground.pcd ref_ng.pcd --min-f1 0.9
Options: --voxel-size FLOAT, --min-precision FLOAT, --min-recall FLOAT, --min-f1 FLOAT, --min-iou FLOAT
evaluate pipeline
Filter, downsample, evaluate in one 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.
- 3d ago First seen · 302 lines · 70 tokens per session scan A 437279a957e2
cli-anything-cloudanalyzer is a skill published in the GitHub repository HKUDS/CLI-Anything (48,809 stars, last pushed 12d ago), licensed Apache-2.0. It adds 70 tokens to every session and 1,801 once invoked, about $0.0003 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…