veto-routinglisted

Use the Veto CLI to select or execute AI models when a task needs multi-provider routing, structured accept or reject decisions, cost-aware dispatch, provider fallback, or Veto plan execution. Do not use for ordinary repository commands or generic model advice.
oleg-koval/agent-skills · ★ 3 · AI & Automation · score 75

Install: claude install-skill oleg-koval/agent-skills

# Veto routing Use Veto as a model-selection and execution layer. It does not expand the user's authorization, validate generated output, or guarantee quality or cost. ## Before a model call 1. Confirm the CLI is available with `command -v veto`. Inside the Veto source checkout, `go run ./cmd/veto` is an acceptable fallback. Do not install it automatically. When using the fallback, replace `veto` in the commands below with `go run ./cmd/veto`. 2. Inspect configured transports with `veto providers`. Never read, print, or copy credential files from `~/.veto/`. 3. Check whether the objective is safe to send to the configured providers. An admission pass can disclose the objective to more than one provider. Stop when sensitive data is present and provider authorization is unclear. 4. Do not run `veto login`, change provider configuration, or incur an unrequested model call. ## Choose the smallest operation - Selection only: use `veto route --json` and consume the single JSON result. - Route and execute: use `veto run --quiet` only when the user asked for model execution and the selected transport can perform the task. - Quality gate: add `--criteria` when the user supplied concrete acceptance criteria. A requested review fails closed. - Multi-step plan: run `veto exec <plan.md> --dry-run` before execution. Execute only steps already within the user's scope. Set `--kind`, `--ri