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/0-ai-ug/cate/cate-clinpx skills add 0-AI-UG/cate --skill cate-cligit clone --depth 1 https://github.com/0-AI-UG/cateWrote 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/0-ai-ug/cate/cate-cli)<a href="https://agentmods.dev/skills/0-ai-ug/cate/cate-cli"><img src="https://agentmods.dev/badge/skills/0-ai-ug/cate/cate-cli.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 | $0.00034 | $0.01449 |
| Opus 5 | $0.00017 | $0.00724 |
| Sonnet 5 | $0.00007 | $0.00290 |
| Haiku 4.5 | $0.00003 | $0.00145 |
Grade A, and why
cate-cli 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 4d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cate CLI
cate is available inside Cate terminals and agent shells. It talks to the
current workspace and requires the relevant Settings → CLI permission.
Start by listing panels:
cate panel list
When working repeatedly with one panel, select it for the current agent or terminal session:
cate panel set 1a2b3c4d
cate panel current
The selection is isolated by a per-terminal CLI session, so other agents and
terminals keep their own targets. Short ids from panel list
are accepted. Use --panel <id> only as a one-command override. Clear the
selection to return to Cate's automatic focused/grouped resolution:
cate panel clear
Selections can point to any native panel. Browser and terminal commands reject a selected panel of the wrong type instead of silently controlling another panel. If a selected panel was closed, select another panel before continuing.
Browser workflow
Inspect, act, wait, then inspect again:
cate panel set 1a2b3c4d
cate browser open https://example.com
cate browser snapshot -i
cate browser fill @s1e2 [email protected]
cate browser click @s1e3
cate browser wait --url '**/dashboard'
cate browser snapshot -i
Page commands after cate browser use agent-browser's native argv directly:
cate browser snapshot -i --compact
cate browser get text @s1e4
cate browser find role button click
cate browser fill '#email' [email protected]
cate browser press Enter
cate browser scroll down 600
cate browser screenshot --full
cate browser console
cate browser errors
Do not use agent-browser's open semantics by assumption: Cate defines
browser open as opening a new tab. Use navigate only when replacing the
active tab is intentional:
cate browser open https://second.example
cate browser navigate https://replacement.example
cate browser new-panel https://separate.example
Cate owns browser identity and presentation. Native session/CDP switching, native tab management, upload/download paths, batch, setup, servers, and browser startup flags are unavailable. Use Cate's lifecycle commands:
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.
- 4d ago First seen · 192 lines · 34 tokens per session scan A cad7c9fe4444
cate-cli is a skill published in the GitHub repository 0-AI-UG/cate (2,118 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,449 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
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
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.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
web-browser
Automate and interact with web pages through Chrome or Chromium using the Chrome DevTools Protocol (CDP): navigate, click, fill forms, inspect content, take screenshots, and debug console or network activity. Use when an agent needs a real browser. Prefer headless Chrome unless visible browser interaction is required.
traceway-setup
Analyze and instrument repositories for Traceway observability. Use when the user wants to plan, add, migrate, or verify Traceway or OpenTelemetry monitoring for backend, browser, full-stack, mobile or iOS, or AI-agent software, including project topology and user-approved setup-plan creation. Backends use OTLP/HTTP…