omni-settings

Read and update global application settings: system prompts, thinking budget, IP filters, payload rules, combo defaults, and require-login configuration.

1,006
installs: 0 up / 0 down, score 0.00
votes: 79,391
repo stars
Updated: less than a month ago
In the catalog since: 25 Oct 2026
From: cheaper-inference/omniroute

Get it through your agent npx skills add cheaper-inference/omniroute@omni-settings

Skill instructions

Rendered from the published SKILL.md, 181 lines.

Overview

Read and update global application settings: system prompts, thinking budget, IP filters, payload rules, combo defaults, and require-login configuration.

Authentication

All requests require a valid Bearer token or session cookie. Obtain a token via POST /api/auth/login or configure REQUIRE_API_KEY=false for local development.

Endpoints

Show the whole skill (61 more lines)

Payloads

See the full OpenAPI specification at GET /api/openapi/spec or docs/openapi.yaml for detailed request/response schemas.

GET /api/settings/thinking-budget — behavior

Returns proxy-level thinking/reasoning request rewrite settings:

Field	Meaning
`mode`	`passthrough` (leave client reasoning alone — required for Codex visible thinking), `auto` (strips all client thinking fields), `custom`, `adaptive`
`customBudget`	Fixed budget when `mode=custom`
`effortLevel`	Base effort when `mode=adaptive`

Not compression and not "decrypt encrypted reasoning". Full guide: docs/guides/THINKING_BUDGET.md.

Example — keep client-controlled reasoning (Codex/Desktop):

curl -X PUT https://localhost:20128/api/settings/thinking-budget \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"passthrough","customBudget":10240,"effortLevel":"medium"}'

Warning: mode=auto deletes reasoning / reasoning_effort / Claude thinking from the outbound body before upstream. That can empty thinking panels even when the client requested Ultra + summary.

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "omni-settings"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Source repository cheaper-inference/omniroute
Listing on skills.sh

From cheaper-inference/omniroute via skills.sh

Related skills

omni-auth
Manage API key authentication and session tokens. Start here to authenticate requests via Bearer token, obtain session cookies, and configure login requirements for the OmniRoute API.
1,081 installs
omni-providers
Manage provider connections, API keys, OAuth flows, and connection tests via the REST API. List, add, update, remove, and test AI provider integrations across OmniRoute's 375-provider catalog.
1,107 installs
minimal-api
.NET 10 minimal APIs — the default for building HTTP endpoints. Covers MapGroup, endpoint filters, TypedResults, OpenAPI metadata, parameter binding, and route conventions. Load this skill when creating API endpoints, configuring routing, setting up OpenAPI documentation, or when the user mentions "endpoint", "MapGet", "MapPost", "MapGroup", "TypedResults", "route", "minimal API", "OpenAPI", "swagger", "rate limiting", or "output caching".
2,805 installs
configuration
Configuration patterns for .NET 10 applications. Covers the Options pattern, IOptionsSnapshot vs IOptions, secrets management, and environment-based configuration. Load this skill when setting up application configuration, managing secrets, binding configuration sections, or when the user mentions "configuration", "appsettings", "Options pattern", "IOptions", "IOptionsSnapshot", "secrets", "user secrets", "environment variables", "connection string", or "config binding".
2,791 installs
gke-alert-configuration
Configures alerting policies in Terraform for Google Kubernetes Engine (GKE) clusters, workloads, and services using PromQL and Google Cloud Managed Service for Prometheus. Use when writing, analyzing, validating, or deploying Terraform alerting policies to monitor GKE service latency, traffic, error rates using Multi-Window Multi-Burn-Rate SLO alerts, memory saturation, and cluster health such as CrashLoopBackOff and Node NotReady conditions. Don't use for non-GKE compute runtimes such as standalone Compute Engine VMs or standalone Cloud Run services without GKE.
3,599 installs