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/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.00000 | $0.00537 |
| Opus 5 | $0.00000 | $0.00269 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cli-anything:test Command
Run tests for a CLI harness and update TEST.md with results.
CRITICAL: Read HARNESS.md First
Before running tests, read ./HARNESS.md. It defines the test standards, expected structure, and what constitutes a passing test suite.
Usage
/cli-anything:test <software-path-or-repo>
Arguments
-
<software-path-or-repo>- Required. Either:- A local path to the software source code (e.g.,
/home/user/gimp,./blender) - A GitHub repository URL (e.g.,
https://github.com/GNOME/gimp,github.com/blender/blender)
If a GitHub URL is provided, the agent clones the repo locally first, then works on the local copy.
The software name is derived from the directory name. The agent locates the CLI harness at
/root/cli-anything/<software-name>/agent-harness/. - A local path to the software source code (e.g.,
What This Command Does
- Locates the CLI - Finds the CLI harness based on the software path
- Runs pytest - Executes tests with
-v -s --tb=short - Captures output - Saves full test results
- Verifies subprocess backend - Confirms
[_resolve_cli] Using installed command:appears in output - Updates TEST.md - Appends results to the Test Results section
- Reports status - Shows pass/fail summary
Test Output Format
The command appends to TEST.md:
## Test Results
Last run: 2024-03-05 14:30:00
[full pytest -v --tb=no output]
**Summary**: 103 passed in 3.05s
Example
# Run all tests for GIMP CLI
/cli-anything:test /home/user/gimp
# Run tests for Blender from GitHub
/cli-anything:test https://github.com/blender/blender
Success Criteria
- All tests pass (100% pass rate)
- TEST.md is updated with full results
- No test failures or errors
[_resolve_cli]output confirms installed command path
Failure Handling
If tests fail:
- Shows which tests failed
- Does NOT update TEST.md (keeps previous passing results)
- Suggests fixes based on error messages
- Offers to re-run after fixes
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 · 74 lines · 0 tokens per session scan A 97c8e1fca0be
test is a command published in the GitHub repository HKUDS/CLI-Anything (48,669 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 537 tokens. 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.