Karpathy Skills vs Together AI Inference Stack 2.0

“I've noticed a measurable improvement in Claude Code session quality after installing this. The 'verify before ending' principle alone has saved me from shipping broken refactors. It's a one-file install that acts like pair programming guardrails from someone who has thought deeply about LLM failure modes.”

“The primitive is clean: a routing layer that accepts a policy object instead of a model name, and resolves the right model at inference time. That's the right DX bet — you put the complexity in a declarative config, not in your application logic, which means you're not writing if-cost-lt-x-use-model-y spaghetti in your own codebase. The moment of truth is whether the policy API is expressive enough to handle edge cases like 'fast for < 50 tokens, quality for > 200' — the blog post gestures at this but the actual parameter surface needs hands-on testing. This is not something a weekend script replaces; real multi-model routing with fallback, retries, and cost accounting is at least three weeks of glue code. Shipping because the abstraction is placed at the right layer, not dressed up as a platform you have to adopt wholesale.”

“This is four bullet points in a markdown file. The signal-to-hype ratio here is completely off — 1,400 stars for something you could write yourself in ten minutes. The underlying principles are sound, but attributing them to Karpathy as a canonical plugin feels like name-dropping disguised as engineering.”

“Direct competitors are OpenRouter and the routing layer baked into LiteLLM — both of which have been doing model routing longer and have wider model catalogs. Together's differentiation is that they own the inference infrastructure underneath, meaning the routing isn't just load-balancing between third-party APIs — they can actually optimize at the hardware level, which is a real and defensible edge. The scenario where this breaks: enterprise customers with strict data residency or model-pinning requirements, where 'let the router decide' is politically untenable regardless of how good the policy engine is. What kills this in 12 months isn't a competitor — it's OpenAI and Anthropic shipping their own tiered quality/speed endpoints natively, which removes the need to route between providers entirely. Still shipping because the infra ownership angle is real, not marketing.”

“The interesting meta-signal here is that the AI community is converging on a shared vocabulary for agent behavior principles. CLAUDE.md-as-skill-format is becoming a de facto standard for distributable agent instructions. This project is early evidence that the best agent tooling might be curated wisdom, not code.”

“The thesis is specific and falsifiable: within 3 years, production AI applications will be heterogeneous-model by default, and hardcoding a single model will look as naive as hardcoding a single database server. That bet is well-supported by the trajectory of model proliferation — we went from 2 viable frontier models to dozens in 18 months, and the trend is acceleration, not consolidation. The second-order effect that matters here isn't cost savings — it's that routing intelligence becomes the new moat layer: whoever owns the policy engine that decides which model runs owns the relationship with the developer, not the model provider. Together is early on this trend, not on-time, which means they have 12-18 months to build enough workflow stickiness before the hyperscalers ship routing as a commodity feature. If this works, the infrastructure state is: Together is the BGP of AI inference — invisible, critical, and deeply embedded in every production stack.”

“For non-engineers using Claude Code to build things, having these guardrails prevents the most frustrating failure modes — the model that goes off and rewrites everything when you wanted one small change. Lowering that friction makes AI coding tools actually usable for creative people who aren't professional developers.”

“The buyer is a platform engineering team or AI infrastructure lead at a company already spending five figures monthly on inference — this isn't for hobbyists, it's for people who have already felt the pain of over-spending on GPT-4 for tasks that GPT-4o-mini handles fine. The pricing scales with usage which is correct alignment, though the real risk is that cost-optimization features commoditize the value prop: if Together routes you to cheaper models efficiently, they're optimizing their own revenue downward, which creates a structural tension. The moat is the combination of owned infrastructure plus the routing intelligence trained on real workload data — that's a real data flywheel if they execute. The business survives a 10x model cost drop because the value is operational simplicity, not the raw tokens; that's the right place to be.”