core-llm-routing-and-finops
SolidLLM routing and cost-governance doctrine for {{PROJECT_NAME}}. Covers model-tier floor rules (Opus / Sonnet / Haiku per role), cost-envelope gates, burn-rate monitoring, per-plan token budgets, parent-inheritance trap detection, and routing decision protocols. Use when authoring a plan, dispatching a sub-agent, estimating compute cost for a phase, reviewing token-usage reports, or evaluating tier-policy changes. This is the LLM FinOps Architect archetype's operating manual for the cognitive layer that complements the mechanical hook check_tier_policy.py (ADR-064). Cost is a quality dimension, not a separate concern.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- Canhada-Labs
- Repository
- Canhada-Labs/ceo-orchestration
- Created
- 4 weeks ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
cost-lean-orchestration
Token-efficient model routing for complex engineering sessions. The main model (Opus / Fable, high reasoning) never bulk-reads or explores — it delegates all exploration, bulk file reading, codebase search, log scanning, dependency tracing, and documentation reading to Sonnet subagents that return compact structured findings, and it spends its own tokens only on synthesis, architecture, judgment, and final code. Use this skill in EVERY session that involves reading more than a couple of files, exploring or mapping a codebase, investigating a bug, auditing call sites, reviewing a large diff, digesting logs or docs, or any multi-step engineering task — even if the user never mentions cost, tokens, subagents, or delegation. This is a standing operating discipline, not an on-request feature.
cost-tier-routing
Use BEFORE doing direct file search, bulk reads, data import/export, or routine coding edits in the main conversation. Routes work to the cheapest model that can do it correctly — haiku for search/IO, sonnet for coding, opus for orchestration/architecture. Triggers when about to call Read on >2 files, Grep/Glob across the repo, batch CSV/JSON transforms, or any "where is X / list all Y / count Z" question. Also triggers when the orchestrator (you, on opus) is about to write straightforward code that a sonnet subagent could handle.
cost-routing
Top-level dispatcher that classifies every incoming request into scout / coder / architect tiers BEFORE any tool call. Routes Read, Grep, Glob, file-search, symbol-lookup, "where is X", and "list files matching Y" to haiku-scout. Routes known-location Edit, Write, multi-file refactor, test authoring, and bounded code changes to sonnet-coder. Reserves the main opus context for ambiguous design questions, ADRs, and tradeoff analysis. Use whenever a request lands in the main context and might involve file IO, code search, code edits, or design reasoning — which is almost every turn.