token-optimiser

Routes agent tasks across local, free cloud, and paid LLM tiers using confidence gates.

Updated Sep 20, 2026
One-click install
npx skills add https://github.com/GreenyZA/neo-light --skill token-optimiser-greenyza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: token-optimiser
Source: https://github.com/GreenyZA/neo-light/tree/main/token_optimiser
Command: npx skills add https://github.com/GreenyZA/neo-light --skill token-optimiser-greenyza

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml.

What problem does it solve? Running every agent task on premium LLM APIs wastes tokens and money, while routing everything to weak local models produces poor results. This Skill scores each task for confidence and scope, then routes it to the cheapest viable tier — local GPU, free cloud models, or paid escalation — with governance and learning built in. ## Core Features & Use Cases - 3-Tier Budget Routing: Routes tasks to T1 local llama-server, T2 free cloud models (OpenRouter, NVIDIA NIM, 40+ free models), or T3 paid models based on confidence thresholds (T1 ≥80%, T2 ≥60%, T3 <60%). - BOA + ITIL Governance: A 6-seat Board of Advisors (Architect, Engineer, Researcher, Reviewer, Budget, Executive) with ITIL classification governs tier selection and automatic swarm delegation for non-trivial work (>3 files, >2 modules, >5 tool calls). - Learning Log Calibration: Every routing decision and outcome is appended to a JSONL learning log to calibrate confidence scoring over time. - Use Case: A developer asks the agent to fix a typo, write unit tests, and add OAuth2 authentication. The Skill routes the typo fix to a free T2 model, the tests to T2, and the security-sensitive OAuth work to T3 with a stripped prompt, logging each decision. ## Quick Start Ask the agent to route this task with the token optimiser, or invoke /token-optimiser before describing your task to get a Token Budget Plan and tiered routing decision.

Frequently Asked Questions about token-optimiser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route LLM tasks to cheaper models automatically?▼

The router scores each task for category, scope, and confidence, then assigns it to T1 local, T2 free cloud, or T3 paid tiers. Tasks at 80% confidence or higher use cheap paths, while anything below 60% escalates to paid models with a stripped prompt.

What free LLM models can I use instead of paid APIs?▼

The T2 tier connects to OpenRouter and NVIDIA NIM gateways offering 40+ free models including NVIDIA Nemotron 3 Ultra, DeepSeek V4 Flash, and Poolside Laguna S 2.1. A category-to-model preference map picks the best free model per task type.

Can I force tasks to stay on a local model for privacy?▼

Yes, privacy and offline keywords like air-gapped, local only, or no cloud force routing to the T1 local llama-server regardless of free-tier priority settings. No data leaves the machine when privacy_force_t1 is enabled.

When does the router escalate tasks to paid models?▼

Escalation to T3 happens when confidence falls below 60% or when security, auth, or credential tasks exceed the 55% confidence cap. Security categories always route to the highest tier with human review flags.

How does automatic swarm delegation decide worker counts?▼

The governance layer triggers swarming when a task touches more than 3 files, more than 2 modules, or more than 5 sequential tool calls. It validates worker sizing, task independence, and paired reviewer assignment before approving delegation.

Why did my task route to a paid tier unexpectedly?▼

Low confidence scores, security-related keywords, or unmatched task categories push routing toward T3. Check the learning log entry for the task to see the matched categories, confidence percentage, and threshold rationale.