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-intelwatchnpx skills add HKUDS/CLI-Anything --skill cli-anything-intelwatchgit clone --depth 1 https://github.com/HKUDS/CLI-AnythingWrote 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/skills/hkuds/cli-anything/cli-anything-intelwatch)<a href="https://agentmods.dev/skills/hkuds/cli-anything/cli-anything-intelwatch"><img src="https://agentmods.dev/badge/skills/hkuds/cli-anything/cli-anything-intelwatch.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.00357 |
| Opus 5 | $0.00017 | $0.00179 |
| Sonnet 5 | $0.00007 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
cli-anything-intelwatch 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 4d 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.
What it actually says
cli-anything-intelwatch
Intelwatch bridges the gap between hacker OSINT and B2B Sales/M&A data. It executes complex financial data aggregation, technology stack detection, and AI-powered due diligence in seconds.
Installation
This CLI is installed as part of the cli-anything-intelwatch package:
pip install cli-anything-intelwatch
Prerequisites:
- Node.js >=18 must be installed and accessible via
npx - Run
node -vandnpx -vto ensure your system meets the requirements
Usage
Basic Commands
# Show help
cli-anything-intelwatch --help
# Generate a deep profile for a company
cli-anything-intelwatch profile kpmg.fr
# Generate a profile with AI Due Diligence
cli-anything-intelwatch profile kpmg.fr --ai
For AI Agents
When using this CLI programmatically:
- Provide the domain name (e.g.,
doctolib.fr) - Use the
--aiflag to let Intelwatch perform due diligence automatically - The output is human-readable and provides a deep breakdown of the company
- Ensure
npxis available on the machine
Example Scenarios
- M&A Due Diligence:
cli-anything-intelwatch profile company-name.com --ai - Sales Intelligence:
cli-anything-intelwatch profile target-client.com
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.
- 4d ago First seen · 51 lines · 35 tokens per session scan A 4dd0e2a55361
cli-anything-intelwatch is a skill published in the GitHub repository HKUDS/CLI-Anything (48,809 stars, last pushed 13d ago), licensed Apache-2.0. It adds 35 tokens to every session and 357 once invoked, about $0.0002 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…