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/omnigent-ai/omnigent/cli-setup-verifynpx skills add omnigent-ai/omnigent --skill cli-setup-verifygit clone --depth 1 https://github.com/omnigent-ai/omnigentWhat 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.00176 | $0.03175 |
| Opus 5 | $0.00088 | $0.01588 |
| Sonnet 5 | $0.00035 | $0.00635 |
| Haiku 4.5 | $0.00018 | $0.00317 |
Grade E, and why
cli-setup-verify scanned grade E with 3 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 3d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
The Omnigent CLI's first impression is: `curl | sh` → run `omnigent` → pick a Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
inspection, `rm -rf` it when done. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
The Omnigent CLI's first impression is: `curl | sh` → run `omnigent` → pick a How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verifying the Omnigent CLI setup & UX in a closed loop
The Omnigent CLI's first impression is: curl | sh → run omnigent → pick a
model credential → start a session. This skill lets an agent enter that flow,
examine the UI/UX, and prove whether a change is verifiable — without a
browser, without real credentials, and without ever touching the developer's
real ~/.omnigent.
The engine is verify_cli.py (next to this file). It drives the real
omnigent binary through a pseudo-terminal (pexpect) inside a throwaway
sandbox, captures what renders, runs assertions, and prints one machine-readable
SUMMARY {json} line.
The whole point is a verifiable loop, not a one-shot check:
- Run a scenario on the unfixed code → baseline (
--label before).- Make the change.
- Run the same scenario →
--label after.- Diff the two
SUMMARYlines. A fix is "verifiable" only if a concrete check or note flips between the two runs. If it doesn't flip, you can't prove the fix did anything — go back to step 2.
Why this is safe (read first)
The real ~/.omnigent here can be many GB (chat DB, runner logs, native
harness state). The sandbox isolates every write three ways:
HOMEis redirected into the sandbox by default. This is the load-bearing one.OMNIGENT_CONFIG_HOME/OMNIGENT_DATA_DIR(omnigent/cli.py_CONFIG_HOME_ENV_VAR/_DATA_DIR_ENV_VAR) redirect config + data — but the CLI's diagnostics logger ignores them: it writes a per-invocationcli-*.logunderstate_dir(), hardcoded toPath.home()/.omnigent/logs(omnigent_ui_sdk/terminal/_config.py). So only redirectingHOMEkeeps a non-help command (config list, the setup PTY spawns,server stop) from writing into the real home. The driver does this for you.--strip-pathreducesPATHsonode/tmux/claude/codexread as "not installed" → the true fresh-machine cold start.- Ambient model keys (
ANTHROPIC_API_KEY, …) are stripped from the child env unless you pass--keep-env-creds.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 211 lines · 176 tokens per session scan E 48ded57cb1fb
cli-setup-verify is a skill published in the GitHub repository omnigent-ai/omnigent (9,591 stars, last pushed yesterday), licensed Apache-2.0. It adds 176 tokens to every session and 3,175 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it E with 3 findings (downloads and executes remote code, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agent-production-validator
Agent skill for production-validator - invoke with $agent-production-validator.
inspector-workbench
Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions, launcher, Home, Threads, Playground, Memory, or any visual behavior in @copilotkit/web-inspector. Don't…
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
typescript-testing
Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, and runtime E2E tests. Use when adding tests, diagnosing TypeScript CI, choosing a focused test command, or validating TypeScript package changes. Do not use for Python-only checks.
agent-integration
Run all three agent integration phases sequentially: research, write-tests, and implement using E2E-first TDD (unit tests written last). For individual phases, use /agent-integration:research, /agent-integration:write-tests, or /agent-integration:implement. Use when the user says "integrate agent", "add agent…