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.
git clone --depth 1 https://github.com/olo-dot-io/Uni-CLIWrote 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/commands/olo-dot-io/uni-cli/verify)<a href="https://agentmods.dev/commands/olo-dot-io/uni-cli/verify"><img src="https://agentmods.dev/badge/commands/olo-dot-io/uni-cli/verify/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/commands/olo-dot-io/uni-cli/verify"><img src="https://agentmods.dev/badge/commands/olo-dot-io/uni-cli/verify.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.00000 | $0.00297 |
| Opus 5.5 | $0.00000 | $0.00119 |
| Sonnet 5.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 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.
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.
- 1mo 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 (235 stars, last pushed 2d 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
checkpoint
Write a new link in the continuum chain summarizing decisions/changes since the last link.
design-qa
Agent-driven design QA — walk the running app, judge design/UX, and drop a Comment-Mode comment on every issue (visible to the human as pins). Then read the session back and fix everything in bulk. Optional focus argument steers the pass.
dream
Roll up the last N links into a single phase-digest link; originals move to archived/ (never deleted).
review-session
Arm-2 — critique the current/last session for efficiency & quality, emit a Zone-A distillation, offer a deliberate GitHub feedback report.
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.