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 skills add alrcatraz/astra-aigate --skill cli-evalgit clone --depth 1 https://github.com/alrcatraz/astra-aigateWrote 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/alrcatraz/astra-aigate/cli-eval)<a href="https://agentmods.dev/skills/alrcatraz/astra-aigate/cli-eval"><img src="https://agentmods.dev/badge/skills/alrcatraz/astra-aigate/cli-eval/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/skills/alrcatraz/astra-aigate/cli-eval"><img src="https://agentmods.dev/badge/skills/alrcatraz/astra-aigate/cli-eval.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.00034 | $0.01491 |
| Opus 5.5 | $0.00014 | $0.00596 |
| Sonnet 5.5 | $0.00007 | $0.00298 |
| Haiku 4.5 | $0.00003 | $0.00149 |
Grade A, and why
cli-eval 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.
This is a copy
100% identical to cli-eval — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Create and run evaluation suites, watch live benchmark progress, view scorecards, compare model performance, and integrate eval runs with CI workflows from the CLI.
Quick install
npm install -g omniroute # or: npx omniroute
omniroute --version
Subcommands
eval
Example:
omniroute eval
eval suites
Example:
omniroute eval suites
eval list
Example:
omniroute eval list
eval get <suiteId>
Example:
omniroute eval get <suiteId>
eval create
Flags:
--file <path>
Example:
omniroute eval create
eval run <suiteId>
Flags:
-m, --model <id>--combo <name>--concurrency <n>--tag <tag>--watch
Example:
omniroute eval run <suiteId>
eval list
Flags:
--suite <id>--status <s>--since <ts>--limit <n>
Example:
omniroute eval list
eval get <runId>
Example:
omniroute eval get <runId>
eval results <runId>
Flags:
--failed
Example:
omniroute eval results <runId>
eval cancel <runId>
Flags:
--yes
Example:
omniroute eval cancel <runId>
eval scorecard <runId>
Example:
omniroute eval scorecard <runId>
simulate [prompt]
Flags:
--file <path>-m, --model <id>--combo <name>--reasoning-effort <level>--thinking-budget <n>--explain
Example:
omniroute simulate [prompt]
OmniRoute — CLI Evals
Requires the omniroute CLI. See CLI entry-point skill for install + global flags.
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 · 264 lines · 34 tokens per session scan A f42f846a4471
cli-eval is a skill published in the GitHub repository alrcatraz/astra-aigate (1 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,491 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to cli-eval, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.