Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ItamarZand88/CLI-Anything-WEB/plugin install cli-anything-webWrote 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/commands/itamarzand88/cli-anything-web/validate)<a href="https://agentmods.dev/commands/itamarzand88/cli-anything-web/validate"><img src="https://agentmods.dev/badge/commands/itamarzand88/cli-anything-web/validate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/itamarzand88/cli-anything-web/validate"><img src="https://agentmods.dev/badge/commands/itamarzand88/cli-anything-web/validate.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00039 | $0.00868 |
| Opus 5.5 | $0.00016 | $0.00347 |
| Sonnet 5.5 | $0.00008 | $0.00174 |
| Haiku 4.5 | $0.00004 | $0.00087 |
Grade A, and why
cli-anything-web: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 1mo 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRITICAL: Read the Conventions First
Before validating, read ${CLAUDE_PLUGIN_ROOT}/skills/shared/CONVENTIONS.md. It is the single source of truth for every rule the checklist enforces (HARNESS.md is the navigational overview that indexes it).
CLI-Anything-Web: Validate Standards
Read the methodology overview: @${CLAUDE_PLUGIN_ROOT}/HARNESS.md
Target: $ARGUMENTS
Process
Skills used:
standards(tiered checklist validation)
- Parse the target path to extract
<app>name - Resolve the
agent-harness/root andcli_web/<app>/package path - Tier 1 fail-fast first — critical checks must all pass before anything else:
Non-zero exit = Tier 1 failures. Fix them and re-run before continuing.python ${CLAUDE_PLUGIN_ROOT}/scripts/validate-checklist.py \ <app>/agent-harness --app-name <app> --auth-type <auth-type> --tier1-only - Full checklist run (both tiers; Tier 2 failures are warnings unless
--strict):python ${CLAUDE_PLUGIN_ROOT}/scripts/validate-checklist.py \ <app>/agent-harness --app-name <app> --auth-type <auth-type> - Run the smoke test for post-install validation:
python ${CLAUDE_PLUGIN_ROOT}/scripts/smoke-test.py cli-web-<app> --auth-type <auth-type> - Review remaining judgment-based checks manually per the standards skill
- Print the report in the format shown at the bottom
- Exit with summary: PASS if no Tier 1 failures (report Tier 2 failures as warnings), FAIL otherwise
Prerequisites
-
npx @playwright/cli@latest --versionsucceeds (playwright-cli available)
Validation Checklist
Invoke the standards skill which runs the complete tiered checklist
across 11 categories:
- Directory Structure (6 checks)
- Required Files (13 checks)
- CLI Implementation (9 checks)
- Core Modules (8 checks)
- Test Standards (8 checks)
- Documentation (3 checks)
- PyPI Packaging (5 checks)
- Code Quality (8 checks)
- REPL Quality (3 checks)
- Error Handling & Resilience (8 checks)
- UX Patterns (4 checks)
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.
- 1mo ago First seen · 100 lines · 39 tokens per session scan A 7417ab0579fd
cli-anything-web:validate is a command published in the GitHub repository ItamarZand88/CLI-Anything-WEB (232 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 868 once invoked, about $0.0002 per session on Opus 5.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
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; run or list flows…
qawolfCliRunResults.template
How to use what qawolf run get --run-id --json returns, and how to read the Playwright trace it links to.
fidelity
Measure how faithfully a clone reproduces a site — pixel-diff plus motion-fidelity into one 0-100 score, a letter grade, a ranked correction plan, and a shareable card.
ai-act-scan-fix
Scan a codebase, then propose concrete remediation (code edits, new files, tests) for the top compliance gaps. Does NOT auto-apply — always shows the plan first.
impact
Which tests a change impacts, with a ready-to-run test command.
archive
Archive extraction boundary analysis. Checks whether CPython's tarfile, zipfile, and shutil.unpackarchive implementations correctly enforce the invariant that no extraction path may write outside the declared destination directory.