# Techtide Cost Aware Model Routing

> Choose models and coding tools with cost, latency, quota, context size, and task risk in mind while preserving verification and quality requirements. Use when an agent needs Alex Cinovoj / TechTide live-coding patterns, tool routing, guarded prototype-to-production workflows, or cross-harness prompt/skill adapters.

- Skill: `techtideohio/techtide-cost-aware-model-routing` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add techtideohio/techtide-cost-aware-model-routing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/techtideohio/techtide-cost-aware-model-routing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: TechTideOhio (https://skillmd.com/u/techtideohio)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/techtideohio/techtide-cost-aware-model-routing

---


# TechTide Cost Aware Model Routing

Choose models and coding tools with cost, latency, quota, context size, and task risk in mind while preserving verification and quality requirements.

## Source Pattern

This skill is distilled from sanitized Alex Cinovoj / TechTide local workflow patterns. Load `references/source-patterns.md` when you need the source anchors and extraction rationale. Load `references/adapter-map.md` when preparing Cursor, Kiro, Lovable, v0, or Replit companion outputs.

## Workflow

1. Estimate task complexity, context size, expected tool calls, and quality bar before selecting a model.
2. Prefer lower-cost lanes for simple classification, formatting, and local edits.
3. Use stronger reasoning lanes for architecture, security, cross-file changes, and high ambiguity.
4. Track quota and latency symptoms and switch lanes when a model is exhausted or underperforming.
5. Record cost-sensitive decisions without storing raw provider keys or private telemetry.

## Output Contract

Return a concise brief with these fields:

- model/tool choice
- cost rationale
- fallback lane
- verification plan
- verification performed or still required
- security and privacy notes

## Guardrails

- Extract reusable methods, not private local content.
- Do not request or expose credentials, tokens, DSNs, service-role keys, customer data, lead lists, or private business exports.
- Use placeholders for people, accounts, projects, URLs, and datasets unless the user explicitly provides public-safe values.
- Require explicit human approval before production mutation, external-recipient messaging, public deployment, billing changes, or destructive filesystem actions.
- Preserve Alex Cinovoj / TechTide attribution while keeping old repo provenance and unrelated contributor markers out of public artifacts.

## Harness Policy

- Use this as a native `SKILL.md` for Claude Code, Codex, Gemini, and Copilot-compatible exports.
- For Cursor, create a focused project rule or workflow note rather than copying this whole skill as an always-on rule.
- For Kiro, create steering only when the workflow can be made short and inclusion-scoped.
- For Lovable, v0, and Replit, turn the workflow into prompt kits, readiness checklists, and handoff prompts.