Ramsay Research Agent — June 26, 2026

Ramsay Research Agent — June 26, 2026

Frontier model access turned into a government allowlist this week. That's the headline I didn't expect to write in 2026. Below it: token meters that will cost more than a salary, verification finally getting named as the real bottleneck, and vertical agents quietly crossing nine figures of revenue while everyone argued about model launches. Here's what mattered.

Top 5 Stories Today

OpenAI shipped GPT-5.6 'Sol' and then handed the keys to Washington

You can't sign up for the best coding model OpenAI has ever built. You have to be approved. By the federal government. One customer at a time.

OpenAI previewed GPT-5.6 'Sol' on June 26, and the capability story is real: it's a three-model family (Sol the flagship at $5/$30 per million in/out tokens, Terra at GPT-5.5-class for roughly half, Luna the cheap-and-fast tier), Sol sets a new state of the art on Terminal-Bench 2.1, and it adds a new "max" reasoning effort plus an "ultra" mode that spins up subagents for hard work. Normally that's the whole story. Not this time. At the request of the Office of the National Cyber Director and OSTP, OpenAI limited access to roughly 20 government-vetted partners, with the administration approving access "customer by customer during this preview period," per Sam Altman's note to staff. All three models are rated High for Biological/Chemical and Cybersecurity risk under OpenAI's Preparedness Framework.

This follows the export-control order that forced Anthropic to pull Mythos and Fable two weeks ago, and that standoff is still unresolved. Two frontier labs, same week, both gated through federal review. That's not a coincidence anymore. It's a pattern.

Independent evaluator METR published its predeployment assessment of Sol the same day, timed to the High-risk designations, which means you get a first-party system card and an outside read on launch day. Good. We need that.

Here's what builders should actually take from this. If your product's moat depends on a single frontier model, your moat now depends on a government approval process you don't control and can't predict. Developer sentiment is already hardening: "if the government allows, you get access, if not, you're out of luck." Some suspect the gating is cover for compute scarcity, not pure safety. I don't know which it is. What I do know is the practical move: keep an open-weights fallback wired and tested. GLM-5.1, Kimi, whatever fits your task shape. Not because open weights are better. Because conditional access is a real failure mode now, and the teams that route around it will keep shipping while the rest wait for a permission slip.

The bottleneck stopped being code generation. It's verification.

I've felt this for months and couldn't name it cleanly. Hacker News named it for me this week. The binding constraint in AI-assisted coding is no longer how fast you can generate code. It's how fast you can verify it.

The HN consensus crystallized around a specific shape: the developers getting real value orchestrate multiple bounded workflows instead of handing an agent one big autonomous task, and they treat pricing, session limits, context retention, and harness design as the product itself, not side issues. Traversal CEO Anish Agarwal put it the same way on the Stack Overflow podcast: AI made writing code cheap and made running it safely in production harder. The bottleneck moved to debugging and incident response.

Then the money agreed. Patronus AI raised $50M to build simulated "digital worlds" that stress-test autonomous agents, with investors citing nearly insatiable demand. Agent evaluation is now its own fundable infrastructure category. And the most human data point of all: Ford, to celebrate topping JD Power's quality ranking, admitted it had to rehire veteran "gray beard" inspectors after its automated quality systems fell short. Judgment-heavy verification work is proving genuinely hard to automate away. That story hit 595 points on HN for a reason.

So what do you do Monday morning? Stop optimizing for generation speed. You already have more code than you can check. Invest the marginal hour in your eval and verification harness, not your prompt library. Break big autonomous tasks into bounded workflows with explicit stop and verify conditions. If you're picking what to learn next, learn to build the thing that catches the agent's mistakes, because that's the scarce skill now. Timothy B. Lee framed it well: saying LLMs take no skill is like saying management has no learning curve because employees do what you say. The judgment is the job.

Gartner says your AI coding bill will pass a developer's salary by 2028

The meter is always running. That's the line from Gartner's June 24 prediction, and it's the one that should change how you build. By 2028, Gartner expects the per-developer cost of AI coding agents to exceed the average developer's salary, driven by consumption-based token pricing and agents that burn tokens on every single action.

Most enterprises underestimate this badly. Gartner notes many vendors lack transparency into how tokens are even metered, and recommends governance frameworks, context engineering, and routine token-usage reviews. This isn't abstract. A widely-debated HN essay, "Why Current LLM Costs Are Not Sustainable," hit 107 points and 189 comments arguing today's prices are propped up by VC and hyperscaler cross-subsidies, with providers absorbing 90%+ of the true cost of every token. Per-token prices have fallen ~10x annually since 2021 even as some workloads grew ~100x in consumption. That's the LLM cost paradox: unit prices drop, your bill explodes anyway.

The counter already exists. Weave Router hit 130 points on HN by embedding each request with a small in-process ONNX model, scoring it against frozen intent-cluster centroids, and routing to the cheapest model that historically matched the frontier on that cluster. The team claims 60-70% of Claude Code requests are short, structurally simple completions an open-source model handles at parity, at roughly one-fortieth the cost. Token-compression middleware is becoming a standard install-once layer (rtk, headroom, LeanCTX all claim 60-95% reductions).

Here's the reframe: token discipline is not a billing footnote, it's a first-class engineering constraint, same as memory or latency. Treat context like a budget. Route cheap work to cheap models. Compress tool output before it hits the window. The teams that bake this in now won't get the 2028 invoice that makes their CFO question the whole program.

Vertical AI agents quietly crossed $100M ARR while we argued about models

These aren't pilots anymore. Sierra reports $150M+ ARR within eight quarters of launch (on $950M raised), Intercom's Fin crossed $100M+ ARR resolving ~2M issues a week, and EliseAI sits around $100M ARR on $250M raised. Three companies selling completed work instead of seats, all at genuine commercial scale.

The structural shift underneath: 47% of the top 500 U.S. enterprises moved at least one business process from traditional SaaS to a vertical AI agent across 2024-2025, up from just 11% in 2023. CIOs are managing a forced re-platforming they didn't ask for. And the incumbents are disclosing their own agent revenue now, which tells you it's material: ServiceNow claims ~$600M of agentic revenue, Salesforce ~$169M growing 800% YoY, Workday $400M of its $8.8B ARR. Still single-digit percentages of total ARR, so the incumbents are monetizing AI as an add-on, not yet seeing it cannibalize the core. The displacement is real but the transition is early. Both things are true.

The wedge is consistent: deep domain integration plus outcome-aligned pricing. A single branded agent replacing a multi-seat support or CRM deployment. You see the same logic in Salesforce shipping Agentic Advisor defensively because AI notetakers Jump and Zocks are capturing the advisor-client relationship and bypassing the CRM entirely. When the AI lives in the meeting, the system-of-record becomes a passive database.

If you're building, the takeaway is sharp. Per-seat pricing in a category an agent can do end-to-end is a depreciating asset. The companies winning sell the outcome (resolved ticket, leased apartment, closed deal) and price against the labor they replace, not the login count. Pick a narrow vertical, integrate deeper than an incumbent reasonably can, and charge for results.

Five major vendors quietly killed peer-to-peer agent chat. If yours still does it, you're behind.

The 2024 idea was that more agents talking to each other equals more intelligence. GroupChat. Everyone wired their agents to message each other. That pattern just lost, and it lost decisively.

Anthropic, OpenAI, AutoGen, Cognition, and LangChain independently settled on the same default: one orchestrator that owns full conversation context, spawning ephemeral isolated subagents that return compressed summaries with no peer-to-peer chatter. Five vendors, no coordination, same conclusion. When that happens it's usually because the alternative stopped working in production. Latent Space is calling the broader moment "Meta-Harness Summer", the shift from building individual harnesses to building harnesses that compose other harnesses.

There's math underneath the convergence now too. A new study on the Co-Failure Ceiling tested 67 frontier models and proved multi-model systems (routing, voting, cascades, mixture-of-agents) can never exceed accuracy of 1 minus beta, where beta is the rate at which every model is wrong on the same query. The usual diagnostic, average pairwise error correlation, can't even identify beta, which means a lot of reported ensemble gains are chasing improvements that are mathematically unreachable. Peer-to-peer chatter doesn't beat that ceiling. It just spends more tokens hitting it.

The production survivors back this up. Roughly 40% of multi-agent pilots collapse within six months, and the post-mortems show every surviving system uses a structured "P2" contract for orchestrator-to-subagent handoffs: explicit objective, required output format, tool guidance, hard task boundaries, dedicated system prompt. Loose "go figure it out" delegation is the failure mode.

What to do: if your agents message each other directly, rip it out. Move to one orchestrator with a near-empty context that fans out to isolated subagents, each handed a typed request like an API call, each returning a 1,000-2,000 token condensed summary. Measure your beta before you invest in any orchestration layer. It's one number, and it tells you whether the layer can possibly pay off.

Security

Amazon Q turned git clone into cloud RCE — CVE-2026-12957, CVSS 8.5. Wiz Research disclosed that Amazon Q Developer auto-launched MCP servers defined in a repo's .amazonq/mcp.json, so a single config file in a cloned repo could execute code with your live AWS keys, cloud CLI tokens, and SSH agent attached. Reported April 20, fixed May 12, public writeup June 26. No known exploitation, but it's a textbook "repo config equals code execution" failure. The defense is concrete: treat any MCP config shipped inside a repo as untrusted code, disable auto-start of repo-defined servers, require explicit approval before spawning them.

The config file is the new attack surface, across every IDE. The Amazon Q bug is one instance of a 2026 pattern: MCP configuration carried in repositories is now an RCE supply-chain vector, not just untrusted tool output. Cursor, VS Code, Windsurf, Claude Code, and Gemini-CLI are all vulnerable to MCP-based auto-launch attacks (Windsurf reportedly exploitable with zero user interaction). VIPER-MCP's scan of ~40K repos produced 67 CVEs. We solved this for package managers with lockfiles and signatures. The MCP config layer has none of that yet.

ShareLock splits one malicious prompt across multiple tools so no single one looks bad. Researchers introduced ShareLock, a tool-poisoning attack against MCP that distributes a malicious instruction across several tool descriptions, defeating the assumption that a reviewer reading one tool will catch it. Per-tool review is now insufficient. The attack surface is the combination, not the individual tool. Pin a known-good baseline for each registered tool's description and diff against it.

North Korea backdoored 144 agent-framework npm packages in 88 minutes. On June 17, an attacker compromised the @mastra npm org via a former contributor's still-active scope access, added a dayjs typosquat as a dependency across 140+ packages, and mass-published 144 malicious versions inside 88 minutes. Combined 1.1M+ weekly downloads exposed. Microsoft attributed it with high confidence to Sapphire Sleet (BlueNoroff/APT38). AI agent frameworks are now first-class supply-chain targets, and stale scope access is still the way in.

2,000 people tried to jailbreak a real AI assistant, and Simon Willison wrote it up. Fernando Irarrázaval ran an open challenge inviting anyone to leak secrets from an OpenClaw test instance, and ~2,000 people attempted it. This is a rare large-scale public data point on how tool-using agents actually hold up under adversarial prompt injection, not a lab benchmark. If you ship agents that hold credentials, read it before you decide your input filter is enough.

Prompt injection reliably games automated résumé screening. A new study shows subtle self-promotional text adding no new qualifications reliably improves an applicant's ranking under LLM screeners, especially when résumé quality is homogeneous and few candidates inject. The adversarial incentive is baked into algorithmic hiring. If you deploy LLM evaluators of any kind, the ranking can be gamed by content, not credentials.

Agents

Semantic early-stopping replaces the arbitrary max_iterations kill-switch. This paper targets the near-universal iteration cap in Writer/Critic loops, calling it a syntactic stop that over-spends on easy inputs and truncates hard ones. The fix halts when consecutive draft embeddings stop changing in meaning (cosine distance with a patience window) plus a quality check. Cost tied to convergence instead of a guessed count. If you run iterative refinement loops, this is directly usable today.

10.1% of agent config files are exact cross-repo duplicates. A prevalence study of 10,008 public GitHub repos found 10.1% of tracked agent config paths (rules files, agent definitions, CLAUDE.md-style markdown) are SHA-256 exact duplicates across independent repos, with 75.5% of clone pairs near-identical. Agent configurations are propagating as undeclared, unmanaged shared dependencies. The authors propose a deterministic control plane to version and audit them. If you maintain steering files, treat them like dependencies, not loose docs.

Vercel's AI SDK 7 repositions from prototype glue to production agent infra. AI SDK 7 adds a unified reasoning-effort option, per-tool typed context, MCP Apps support, built-in telemetry, and the headline WorkflowAgent for crash-durable agent runs plus a HarnessAgent API that drives Claude Code, Codex, and Pi from one interface. It targets the reliability gaps that break in-memory agent loops. The "harness outlives the model" framing keeps showing up.

Pydantic AI v2 ships a leaner core and a "Harness" abstraction. Pydantic AI v2 brings type-safety to agent runtimes with a slimmed core and a new Harness for running agents, competing with LangChain and Microsoft's Agent Framework. Same week as Vercel and GitHub all naming the harness layer explicitly. That's three independent "the runtime is the product" signals in seven days.

AWS "agentic overlays": retrofit, don't rebuild. AWS detailed a pattern of thin wrapper layers that turn REST-based enterprise services into agent-callable surfaces without rewriting the underlying systems. It's the pragmatic enterprise reality: core services can't be replaced fast, so you wrap them. A practical architecture for adding agent capability to brownfield estates.

Research

Most of the gap between simple and giant time-series models is preprocessing, not scale. A new paper argues most of the accuracy gap between Ridge regression and large time-series foundation models closes by tuning preprocessing rather than scaling architecture, using Ridge as a closed-form testbed where optimal hyperparameters can be read off directly. A pointed counter to "capacity unlocks accuracy." Exhaust cheap interpretable baselines before reaching for a foundation model.

Multilingual reasoning cascades need carried context to stop bleeding meaning. The standard translate-to-English, reason, translate-back cascade is structurally lossy because each stage discards cultural grounding, register, and disambiguation cues. The authors propose a training-free context-aware cascade that carries extra context across stages. Cheap and immediately applicable if you ship multilingual pipelines.

Daniel Jackson challenges 50 years of object-oriented partitioning. MIT's Daniel Jackson (Alloy, Software Abstractions) argues the core OO principle of partitioning functionality among objects that mirror problem-domain individuals is neither natural nor straightforward, and that later software-engineering developments inherited the same fragmentation they tried to fix. Worth reading if you're rethinking architecture in an era where agents generate most of the code anyway.

Static structure anchors make agent code navigation reproducible. LLM code agents navigate by keyword search and miss call graphs, inheritance, and config dependencies, making navigation stochastic. This study tests injecting stable structural facts as plain-text comments to constrain probabilistic exploration. A low-cost lever for making agent behavior in large repos repeatable across runs.

Infrastructure & Architecture

IBM built a sub-1nm chip with ~100 billion transistors, extending Moore's Law a decade. Per MIT Technology Review, the prototype packs roughly 100 billion transistors on a fingernail-sized area, twice its prior density record. Density gains of this magnitude bend the inference cost curves that increasingly bottleneck frontier deployment. The long-run economics story behind every "tokens are too cheap to last" argument.

Qualcomm bought Modular for $3.92B and named Meta as a data-center CPU customer. At its June 24 Investor Day, Qualcomm agreed to acquire Modular (Mojo language, MAX inference engine, founded by LLVM/Swift creator Chris Lattner) all-stock at $3.92B, and unveiled the Dragonfly C1000 data-center CPUs with Meta as launch customer. It's a ~$14B RISC-V-plus-open-compiler bet to loosen Nvidia/CUDA lock-in. A well-funded Modular could actually move cross-hardware deployment for anyone on Mojo/MAX.

Baseten raised $1.5B at up to $13B as inference becomes the contested layer. Baseten's Series F closed June 22 led by Altimeter, Conviction, and Spark, with revenue up ~20x YoY and more than 1 billion inference calls a day across 87 clusters and 18 clouds. The model layer gets the headlines, but inference at the app layer is where this round says the money is.

The frontier labs' balance sheets are tangled through shared compute. SpaceX's S-1 surfaced that rival Anthropic rents 300MW (~220,000 GPUs) of xAI's Colossus 1 capacity near Memphis for $1.25B a month through May 2029, a contract that could exceed $40B, terminable on 90 days' notice. xAI posted a ~$2.4B Q1 loss against $7.7B capex. Competitors renting each other's GPUs is the strangest, most telling structure of this cycle.

Nx Polygraph gives agents cross-repo visibility and resumable sessions. Nx debuted Polygraph on June 25, a meta-harness that indexes all your repos (private and OSS) into a unified "synthetic monorepo" dependency graph so agents can plan cross-repo work without being told where to look, and resume any session from any developer or machine. It hit Product Hunt's leaderboard and is free for now. It targets two real failure modes: repo-boundary blindness and lost session context.

Tools & Developer Experience

Claude Code 2.1.191 makes /rewind resume from before a /clear. The June 24 release lets you wipe context to start a fresh task, then jump back into the prior thread if you find you still need it. It also makes background-agent stops permanent (no more zombie tasks resurrecting), fixes scroll jumping during streaming, and cuts streaming CPU ~37%. The practical workflow: clear aggressively between tasks to keep context cheap, rewind back only when you actually need the history. A separate late-June fix pass closed background-session env-var bleed and model-restriction leaks into the picker.

IDEs are becoming neutral, multi-provider agent hosts. Apple's Xcode 26.6 added Google Gemini alongside Claude and Codex, all pluggable through the open Agent Client Protocol. Devin Desktop and JetBrains have opened to ACP too. The editor is decoupling from any single model vendor, which pressures tools to compete on agent quality rather than IDE lock-in. Standardize on one protocol and bring whichever agent wins this month.

opensrc pipes dependency source straight into ripgrep for agents. When an agent reasons about a third-party package, types and docs often aren't enough. Pipe opensrc into rg (rg "parse" $(opensrc path zod)) to search the package's actual implementation on demand, fetching and caching on first use. Far lighter than vendoring or cloning a dependency just so the agent can read how it really works.

GSD's --minimal flag cuts Claude Code cold-start tokens 94%. GSD ("Get Shit Done," ~58.9K stars) adds a discuss→plan→execute→verify→ship workflow, and its --minimal flag drops cold-start overhead from ~12K to ~700 tokens. Execution spawns parallel subagents each with a clean 200K context while the main session stays at 30-40% utilization. The transferable lesson: keep the orchestrator's context near-empty, push expensive work into disposable full-context subagents.

Models

Google baked computer use into Gemini 3.5 Flash as a native tool. Google DeepMind shipped computer use as a built-in tool inside Gemini 3.5 Flash on June 24, collapsing the standalone Oct-2025 computer-use model into the same model you already use for function calling, Search grounding, and Maps. One agent sees a screen, clicks, types, and looks something up with no inter-model routing. This is the routing-is-overhead counterpoint to the multi-model story: sometimes the answer is one model that does it all.

The SWE-bench leaderboard has a trust problem: 100 models listed, 1 independently verified. Analysis of the June 2026 SWE-bench Verified leaderboard found llm-stats listing 100 models with only 1 result independently verified, the other 99 vendor-submitted. Current standings show Claude Opus 4.8 leading active SWE-bench Pro at 69.2%, Fable 5 topping overall at 0.800, GLM-5.1 best open-weight at 58.4%. Treat headline numbers as scaffolding-and-vendor-dependent marketing and validate on your own task shapes.

The "Fable 5 is back" rumor was a UI bug. Viral r/ClaudeAI and r/singularity claims that Anthropic's frozen Fable 5 had quietly returned were debunked on June 25: staff said zero Fable/Mythos traffic is being served and model-picker sightings were a UI bug. A clean confirmed-vs-rumored data point, and a reminder of how fixated the community is on the export-control suspension.

Vibe Coding

ponytail hit ~58K stars in two weeks by making agents write less code. DietrichGebert/ponytail, a Claude Code/Cursor skill that makes agents "think like the laziest senior dev in the room," rocketed to ~58,500 stars since launching June 12. It's a YAGNI-driven plugin that biases agents toward deleting and not-writing code, aimed squarely at the over-generation problem. The fact that the fastest-growing coding skill of the month is one that makes the agent do less tells you exactly what builders are fighting.

codebase-memory-mcp says stop telling agents to "read that file." A widely-shared thread is pushing DeusData's codebase-memory-mcp, which indexes a repo into a persistent knowledge graph (158 languages, sub-ms queries, ~99% fewer tokens, the 28M-LOC Linux kernel in ~3 minutes on an M3 Pro). For Claude Code it installs a PreToolUse hook that intercepts Grep/Glob and injects structured context. A concrete instance of the code-comprehension layer becoming standard, alongside oraios/serena, graphify, and zilliztech/claude-context.

"Run an army of agents" control planes are their own category now. superset-sh/superset (12K+ stars) markets itself as a code editor for running an army of Claude Code and Codex instances, while agent-of-empires manages multiple agents from a TUI or web UI. The human control plane (spawn, monitor, steer many agents at once) is now a product separate from the agents themselves. If you're running more than three agents, you'll want one.

Coding agents are becoming app platforms, not just code writers. santifer/career-ops (56K stars) is a full job-search system with 14 skill modes built on Claude Code, and tools like ppt-master and frontend-slides use coding-agent skills to generate real editable PowerPoint decks. The "skill mode" pattern treats Claude Code as an application platform that ships products, not diffs. I'm watching this closely. It's a different mental model than "AI writes my code."

Hot Projects & OSS

General Intuition raised $320M at $2.3B to train action models on gameplay footage. General Intuition closed a $320M Series A on June 25, led by Khosla with Bezos, General Catalyst, Eric Schmidt participating. It trains large action foundation models on action-labeled gameplay from Medal's 17M monthly users and builds world models to generate agent training environments. Most of the round funds compute for the next pre-training run. A genuinely different data bet than the text-and-code crowd.

Google's agents-cli standardizes skill authoring and evaluation. google/agents-cli (~3,100 stars, created April 8) is an official Google CLI plus skills that turn any coding assistant into an expert at creating, evaluating, and iterating on agent skills. Google standardizing skill authoring matters as the format proliferates across Claude Code, Cursor, and Codex. When the platform owners start shipping the meta-tools, the format is real.

SaaS Disruption

Navan is up ~30% in 2026 while public software bleeds. Against an IGV down ~21% YTD, Navan is up roughly 30%, one of the few public B2B leaders gaining. SaaStr's read: the market rewards durable usage and transaction-tied revenue (travel-and-expense) over per-seat names getting re-rated. The "what's different about the winners" question matters more than the stock. Usage-tied beats seat-tied in the agent era, and the public markets are pricing it.

Booking.com built a free expense tool in 6 weeks. Booking.com for Business bundled spend management into its travel workflow rather than charging for it, collapsing willingness-to-pay for a paid category (Concur/Ramp/Brex/Navan-style expense). The lesson is the sequence, not the feature: an incumbent in an adjacent category can make your paid product a free attachment. Free-tier cannibalization just landed in finance SaaS.

"Ship an MCP server or you're behind." Practitioner guides now treat an MCP server as mandatory SaaS packaging in 2026, citing adoption from Anthropic's Nov-2024 launch (~2M monthly SDK downloads) to OpenAI (~22M) to Microsoft Copilot Studio (~45M). The distribution inversion: products win by being callable inside the user's agent rather than owning a destination UI. The marketplace-to-API-to-agent-skill shift hit default status. UI as moat is depreciating fastest.

Design SaaS entered its "frenemies era." Anthropic launched standalone Claude Design, Google unveiled Pics in Workspace, Canva shipped its own foundation model. Incumbents are holding revenue (Figma +41%, Canva +35%, Adobe +11.5%), but the threat is generation-from-intent replacing manual canvas work. Figma's Dylan Field argues AI is a tailwind, not a threat. As someone with 20 years in design, my read: the value is migrating from the editing surface to the prompt. The tool that generates beats the tool you operate, but taste still decides which generation ships.

Policy & Governance

The Mythos standoff is getting worse, not better. The Verge reports Anthropic's situation deteriorating two weeks after it took its Mythos-class models offline following a Friday-evening ultimatum from the Trump administration, negotiations still unresolved. Paired with the GPT-5.6 gating, state involvement in which frontier models can be served is becoming routine. TechCrunch argues the old Anthropic-vs-OpenAI framing is obsolete now that capability is a matter of political consequence. Whatever you think of that, plan for access to be a policy variable.

Engineering is the most AI-resilient job, even as 56% of 2026 layoffs blame AI. SignalFire data shows engineering roles fell only 11% vs 2019 while overall big-tech hiring dropped 25%, and AI-engineer postings rose 654% from H1 2024 to H2 2025. The paradox: 56% of 2026 layoff events (185,894 workers through June 24) cite AI, even as the hyperscalers plan ~$700B in 2026 AI capex. AI-skilled engineers stay in demand while customer-service postings fell 24-28%. The displacement is real and uneven, and "learn to build the thing that verifies the AI" looks like the durable bet.

Frontier-model economics are structurally rough. Dean W. Ball argues models cost an enormous amount to train while only a fraction is recouped in the brief post-release window before the next model or a cheaper competitor erodes pricing power. It's a sharper frame on the GPT-5.6 tiering and the access-control fight than the usual capex headlines. When the window to recoup shrinks, gating access to preserve it starts to look like economics, not just safety.

Skills of the Day

1. Treat the context window as RAM, not storage, and budget to ~50% fill. A recurring 2026 failure is engineers treating context as durable storage. Reliable performance on complex reasoning degrades meaningfully past ~50% of advertised max context, well before the hard limit. Budget prompts to that line and offload everything else to a persistent layer beneath the window.

2. Default your RAG stack to BGE-M3 + BGE-reranker-v2 with hybrid retrieval for a 25-40% precision gain. Wrap naive retrieval with hybrid dense+sparse search plus cross-encoder reranking. The order of operations is metadata filter → hybrid retrieve → rerank, not "embed and top-k." Cache both embeddings and rerank calls.

3. Load tool schemas on demand to cut MCP context overhead 47-90%. Anthropic's Tool Search loads MCP schemas only when needed instead of front-loading all of them, cutting one workflow from 51K to 8.5K tokens. Every definition you keep out of the window until it's called is reliability you buy back above the 50% mark.

4. Enforce must-happen actions with hooks, not prompts. Anything that must run reliably (linter, dangerous-command block, notification) belongs in a settings.json hook that executes deterministically. The rule of thumb: skill for domain logic, subagent for isolated work, hook to enforce a rule with code.

5. Split planning from execution to shrink prompt-injection blast radius. Have a planner decide which tools to call and a separate constrained executor invoke them. Because the executor can't be talked into new actions by injected text, a successful injection can't expand past the pre-authorized plan. Pair with response filtering that strips instruction-like phrases from tool outputs.

6. Grade subagent output with a blind rubric in a fresh context window. Anthropic's Performance Outcomes attaches a grader that scores each result against an explicit rubric in a context that never saw the worker's reasoning, so it judges output on its own terms. Raised internal task-success up to 10 points. Failures bounce the subagent back to revise.

7. Rate-limit agents by tokens, not requests, with hard low caps on destructive tools. A 60-requests-per-minute limit calibrated for humans is no defense against an agent chaining hundreds of calls in seconds. Use token-based limiting plus specific low caps on high-blast-radius actions like send_email, delete_file, make_payment.

8. Force subagents to return validated JSON schema, and hand off at ~60K tokens. Hand each subagent a JSON Schema so it returns a validated object the layer retries on mismatch, eliminating the most common source of cross-agent context loss. Around 60K tokens, fire-and-forget to a fresh agent rather than burning the remaining budget.

9. Use GRPO with verifiable rewards to lift reasoning on fewer than 100 examples. GRPO drops the critic network, generates multiple completions per prompt, and grades them relative to each other. Paired with rule-based verifiers, it can improve reasoning with under 100 examples. Reach for it when your task has a programmatic correctness check, not a fuzzy quality target.

10. Keep root CLAUDE.md under 200 lines and push specifics into subdirectory files. Subdirectory CLAUDE.md files load on-demand only when Claude reads a file beneath that folder, so deep module conventions never inflate context during unrelated work. Reserve the root for build commands and team-wide conventions. It turns the hierarchy into a lazy-loaded context tree instead of one fat always-on prompt.