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/olo-dot-io/uni-cli/unicli-oneshotnpx skills add olo-dot-io/Uni-CLI --skill unicli-oneshotgit 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/skills/olo-dot-io/uni-cli/unicli-oneshot)<a href="https://agentmods.dev/skills/olo-dot-io/uni-cli/unicli-oneshot"><img src="https://agentmods.dev/badge/skills/olo-dot-io/uni-cli/unicli-oneshot.svg" alt="Measured on agentmods" 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.00037 | $0.00335 |
| Opus 5 | $0.00018 | $0.00168 |
| Sonnet 5 | $0.00007 | $0.00067 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
unicli-oneshot 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 6d 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
unicli One-Shot Adapter
Generate a single unicli command from a URL + goal in 4 steps.
Process
Step 1: Open the Page
unicli operate open "<URL>"
unicli operate state
Step 2: Discover the API
Open browser DevTools Network tab. Look for XHR/Fetch requests that return JSON data matching your goal.
Key signals:
/api/or/v1/in URL → REST endpoint- JSON response with array of items → listable data
- Query parameters → filterable
Step 3: Write the YAML
Create src/adapters/<site>/<command>.yaml:
site: <site-name>
name: <command>
description: <what it does>
type: web-api
strategy: public # or cookie if auth needed
pipeline:
- fetch:
url: <discovered-api-url>
params: <query-params>
- select: <path.to.data>
- map:
title: ${{ item.title }}
# ... map fields
columns: [title, ...]
Step 4: Test
npm run dev -- <site> <command>
npm run dev -- <site> <command> -f json
Done. One YAML file, one command, zero code.
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.
- 6d ago First seen · 60 lines · 37 tokens per session scan A 5f261dd6bee0
unicli-oneshot is a skill published in the GitHub repository olo-dot-io/Uni-CLI (270 stars, last pushed 3d ago), licensed Apache-2.0. It adds 37 tokens to every session and 335 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-30.
Other skills, from other repositories
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing…
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
opencli-usage
Use at the start of any OpenCLI session — this is the top-level map of what opencli can do, how to discover adapters, what flags and output formats are universal, and which specialized skill to load next. Point here when an agent asks "what can opencli do?" or "how do I find the right command?".
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.