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/alrcatraz/astra-aigate/cli-setupnpx skills add alrcatraz/astra-aigate --skill cli-setupgit clone --depth 1 https://github.com/alrcatraz/astra-aigateWhat 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.00034 | $0.00892 |
| Opus 5 | $0.00017 | $0.00446 |
| Sonnet 5 | $0.00007 | $0.00178 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
cli-setup 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.
How it starts
The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Run initial setup, configure global CLI settings, manage environment variables, check for updates, and configure autostart via the CLI setup and config commands.
Quick install
npm install -g omniroute # or: npx omniroute
omniroute --version
Subcommands
autostart
Example:
omniroute autostart
autostart enable
Example:
omniroute autostart enable
autostart disable
Example:
omniroute autostart disable
autostart toggle
Example:
omniroute autostart toggle
autostart status
Example:
omniroute autostart status
config
Show or update CLI tool configuration
Example:
omniroute config
config list
List all CLI tools and config status
Flags:
--json
Example:
omniroute config list
config get <tool>
Show current config for a tool
Flags:
--json
Example:
omniroute config get <tool>
config set <tool>
Write config for a tool
Flags:
--model <model>--non-interactive--yes
Example:
omniroute config set <tool>
config validate <tool>
Validate config format without writing
Flags:
--model <model>--json
Example:
omniroute config validate <tool>
config opencode
Generate OpenCode config (alias for
Flags:
--model <model>--non-interactive--yes
Example:
omniroute config opencode
config lang
Example:
omniroute config lang
config get
Flags:
--json
Example:
omniroute config get
config set <code>
Flags:
--force
Example:
omniroute config set <code>
config list
Flags:
--json
Example:
omniroute config list
env
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.
- 2d ago First seen · 270 lines · 34 tokens per session scan A dcf3c458e83a
cli-setup is a skill published in the GitHub repository alrcatraz/astra-aigate (1 stars, last pushed 5d ago), licensed MIT. It adds 34 tokens to every session and 892 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-31.
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…