agentmods.dev

cli-anything-validate

A checklist-based command for checking a CLI-Anything harness, which is a command-line interface built around another application. It reviews the harness structure, implementation, tests, documentation, packaging, and code quality.

In plain words
What is it for?
Use it to validate an existing harness against the CLI-Anything requirements and produce a clear pass-or-fail result with specific gaps.
Why use it?
It helps find missing requirements or defects before a harness is treated as complete, with progress saved so validation can resume.

Command

49k 11d ago A scan 18 tokens original Apache-2.0
View the source file HKUDS/CLI-Anything
Install

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.

agentmods
npx agentmods add commands/hkuds/cli-anything/cli-anything-validate
Clone the repo
git clone --depth 1 https://github.com/HKUDS/CLI-Anything
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 388 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00018 $0.00388
Opus 5 $0.00009 $0.00194
Sonnet 5 $0.00004 $0.00078
Haiku 4.5 $0.00002 $0.00039

Measured 2d ago against content hash 2ea994679eb4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cli-anything-validate 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 2d 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.

cursor-plugin/commands/cli-anything-validate.md · 44 lines

What it actually says

cli-anything-validate Command

Validate an existing harness against directory, implementation, test, docs, packaging, and code-quality requirements.

Target software: local path argument (required).

CRITICAL: Resolve PLUGIN_ROOT (absolute paths only)

  1. Read ~/.cursor/cli-anything-generator.root / %USERPROFILE%\.cursor\cli-anything-generator.root
  2. Else install dir PLUGIN_ROOT.txt / default .../plugins/local/cli-anything
  3. Read {PLUGIN_ROOT}/references/HARNESS.md and {PLUGIN_ROOT}/references/commands/validate.md via absolute paths

Cursor Tool Bindings

Cursor tool Role
Glob / Grep / Read Checklist inventory of harness layout and APIs
Shell Optional smoke tests, import checks, pip show / entry-point checks
Write Only to record validation report if the user asks for a file

Phase Gates and Resume (hard gate)

Progress: {software-root}/agent-harness/.cli-anything-progress.json with "mode": "validate".

  • Walk checklist sections; mark each section completed before moving on.
  • Resume incomplete validation; finish with a clear pass/fail summary and concrete gaps.

Validate checklist (summary)

  • Directory layout under agent-harness/cli_anything/<software>/
  • Implementation: Click + REPL + --json + session patterns per HARNESS
  • Tests: unit + E2E + installed CLI
  • Docs: README, SOFTWARE.md, TEST.md, skills
  • Packaging: namespace packages + console_scripts

What This Command Does

Follow {PLUGIN_ROOT}/references/commands/validate.md. Do not silently lower the quality bar.

Changes

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.

  1. 2d ago First seen · 44 lines · 18 tokens per session scan A 2ea994679eb4

Subscribe to this mod's changes

cli-anything-validate is a command published in the GitHub repository HKUDS/CLI-Anything (48,809 stars, last pushed 11d ago), licensed Apache-2.0. It adds 18 tokens to every session and 388 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.

Code reviewTestingWriting and docs
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

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.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

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.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens