core-llm-routing-and-finops

Solid

LLM 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.

AI & Automation 3 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
20
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# LLM Routing and FinOps ## Opening commitment Cost is a quality dimension, not a separate concern. A plan that "works" but burns ten times the necessary budget has shipped a defect — the defect happens to live in the dispatch graph rather than in the code, but it produces the same kind of regret (post-hoc surprise, hard to reverse, accountable to the same Owner). This skill teaches the LLM FinOps Architect how to reason about routing choices so cost is treated as a first-class invariant alongside correctness, security, and performance. The rule that anchors everything below: **a wrong-tier dispatch is a finding with severity equal to the worst case it enables.** Routing `code-reviewer` to Sonnet on a security-touching diff is not a cost optimization — it is a CRITICAL governance violation that bypasses ADR-052's VETO floor. Routing a one-shot fixture generator to Opus is not safety — it is a MINOR cost finding that, repeated across 30 spawns per session, becomes a MAJOR budget regression. ## What This Skill Is (and isn't) This skill is the **cognitive layer** for routing and cost decisions. It complements but does not replace the mechanical enforcement. | Concern | Mechanism | Layer | Reference | |---|---|---|---| | VETO floor for `code-reviewer` / `security-engineer` is hard-pinned to Opus | Canonical agent files (`.claude/agents/<slug>.md`) carry `model: claude-opus-4-8` frontmatter; `check_agent_spawn.py` PreToolUse Agent matcher validates that file at spawn; agent ...

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

AI & Automation Listed

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.

0 Updated 2 weeks ago
itzTiru
Data & Documents Listed

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.

3 Updated today
The-Artificer-of-Ciphers-LLC
AI & Automation Listed

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.

3 Updated today
The-Artificer-of-Ciphers-LLC