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 commands/olo-dot-io/uni-cli/verifygit clone --depth 1 https://github.com/olo-dot-io/Uni-CLIWhat 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.00000 | $0.00297 |
| Opus 5 | $0.00000 | $0.00148 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
verify 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.
What it actually says
/verify — run full verification pipeline
Run the full Uni-CLI verification gate and report the outcome.
What it does
Executes npm run verify, which chains seven gates in order:
format:check— Prettier formattingtypecheck— TypeScript strict mode,--noEmitlint— oxlint onsrc/lint:context— agent-lint rubric on AGENTS.md / CLAUDE.md / skillsbuild:manifest— regeneratedist/manifest*.jsontest— Vitest unit projectbuild—tsc+ AGENTS.md regeneration
Exits non-zero on the first failure. A clean run produces a compact summary with test count and manifest stats.
Usage
/verify
Ground rules
- Never claim "done" before this passes.
- On failure, show the tail of the output and the first red step.
format:checkfailures: runnpm run formatand re-try.testfailures: investigate root cause; no--bailloops.
Why
CI runs this exact chain on six matrix cells (Node 20/22 × ubuntu/ macos-14/windows). Local green means CI is likely green — but trust CI, not the local run.
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 · 38 lines · 0 tokens per session scan A 25714d656d19
verify is a command published in the GitHub repository olo-dot-io/Uni-CLI (270 stars, last pushed 12d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 297 tokens. 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
toon
A lightweight data format designed to minimize token usage when passing structured data to LLMs.
qa
Dispatch a verifiable browser task to the qa-tester subagent. Use for regression checks, smoke tests, and any task with a clean pass/fail outcome. Supports an EXHAUSTIVE mode that verifies every control behind an honesty gate.
feedback
File a plugin-capability-gap note, or flush queued notes to GitHub issues.
telemetry
Inspect, opt in/out of, and audit mochi's anonymous usage telemetry.
insights
Owner-only — fetch and print the mochi-insight server's aggregate summary.
render
Inspect an archived transcript (gzipped) — show counts, tool calls, errors. Useful after a PreCompact or SessionEnd, before deciding to write a retroactive /continuum:checkpoint.