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 commands/hkuds/cli-anything/cli-anything-testgit 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.00022 | $0.00374 |
| Opus 5 | $0.00011 | $0.00187 |
| Sonnet 5 | $0.00004 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
cli-anything-test 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 yesterday.
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-anything-test Command
Run and document tests for an existing harness.
Target software: local path argument (required).
CRITICAL: Resolve PLUGIN_ROOT (absolute paths only)
- Read
~/.cursor/cli-anything-generator.root/%USERPROFILE%\.cursor\cli-anything-generator.root - Else install dir
PLUGIN_ROOT.txt/ default.../plugins/local/cli-anything - Read
{PLUGIN_ROOT}/references/HARNESS.mdand{PLUGIN_ROOT}/references/commands/test.mdvia absolute paths
Cursor Tool Bindings
| Cursor tool | Role |
|---|---|
| Shell | pytest, installed cli-anything-<software>, environment checks |
| Read / Grep | Locate tests, parse failures, update TEST.md |
| Write / StrReplace | Fix tests or harness bugs uncovered by failures |
Phase Gates and Resume (hard gate)
Progress: {software-root}/agent-harness/.cli-anything-progress.json with "mode": "test".
- Track unit / e2e / installed-CLI / TEST.md update steps; do not skip ahead without marking completion.
- Resume if interrupted; only append passing evidence to
TEST.md. - Prefer
CLI_ANYTHING_FORCE_INSTALLED=1for release-style installed-command checks when documented by HARNESS / test command.
Test checklist
- Run unit + E2E suites
- Verify installed
cli-anything-<software>via subprocess /_resolve_cli - Update
TEST.mdonly with passing results
What This Command Does
Follow {PLUGIN_ROOT}/references/commands/test.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.
- yesterday First seen · 43 lines · 22 tokens per session scan A 99fb1bc3761b
cli-anything-test is a command published in the GitHub repository HKUDS/CLI-Anything (48,669 stars, last pushed 11d ago), licensed Apache-2.0. It adds 22 tokens to every session and 374 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.