SpaceX officially closed its $60B acquisition of Cursor on Friday, and Stripe is reportedly paying $7B+ for OpenRouter. The editor a lot of us live in and the gateway a lot of us route through both changed hands in one week, and neither was bought with your workflow in mind. Inside: how to keep your setup portable, five agent skills worth stealing, and the five frontier models that shipped while you were reading about acquisitions.

Hello Builders! 👋

🔥 This Week's Top Story

Two layers of the builder stack got new owners in five days. Cursor confirmed the SpaceX deal has closed and said the team is joining SpaceXAI to work on Grok. Stripe, meanwhile, is reported to be buying OpenRouter for north of $7 billion, which puts the router most of us use to shop for tokens inside a payments company.

Here is why this matters more than the usual acquisition noise. Your editor and your model gateway were the two pieces you picked on merit, swapped freely, and never thought about again. Now the routing defaults, the pricing, and the data policy behind both are strategy decisions at companies with much bigger games to play. A rocket company wants Grok everywhere. A payments company wants to own the billing rail for every token you spend.

My honest read: nothing breaks next Tuesday. Acquisitions rot slowly, and the r/cursor threads full of "should I be worried" are running well ahead of any actual change. But the cheap hedge costs you an afternoon. Keep your prompts, skills, and agent config in files in your repo instead of inside one vendor's UI. Keep a second gateway configured and know what you spend per provider. Portability is not loyalty, it is leverage.

🧠 Skill to Steal

  • Security Review Skills Your Agent Can Actually Run - Google shipped a modular, stack agnostic toolkit of security review skills for coding agents, so the thing writing your auth flow can also audit it. Point it at your repo this week and let it flag the injection and secrets handling your reviewer skims past. It is the rare skill pack from a team whose day job is being attacked at scale.

  • Turn Any Technical Book Into a Claude Skill - Feed it a PDF and it produces a ready to load Claude Code skill, so your agent studies the book you never finished.

  • Give Your Agent a Disposable Linux VM - Agents get a throwaway machine instead of your laptop, which is the correct answer to "should I let it run that command."

  • One Hub, Many Specialist Agents - Keeps specialists in a hub and spins up a temporary orchestrator per task, instead of one bloated agent that forgets its job.

  • Coding Tools for Any Agent, via MCP - Drops real code editing and navigation into whatever agent you are running, no bespoke harness required.

🚀 Ships & Launches

📰 On the Radar

  • Claude's Invisible Watermarks Get Specific - Anthropic detailed how SynthID style text watermarking will work to satisfy EU transparency rules, including what survives editing and how it treats code. If you ship AI written content or code, assume provenance is now detectable by default and plan your disclosure before a customer asks.

  • Meta Swings Back to Open Weights - Zuckerberg is attacking closed rivals again as Meta returns to open models. Signal: the free tier of capable weights is not going away, so self hosting stays a real option.

  • Google Lets You Turn the Visible Watermark Off - The badge on Gemini images and video can be toggled away, the invisible marker stays. Cosmetic freedom, not deniability.

  • Someone Is Stealing Reasoning Traces From LLM APIs - A demonstration that hidden reasoning can be extracted through the API surface. If your product's value is in the prompt chain, that is a leak path you have not modeled.

📣 Ship & Grow

📺 Learn & Build

  • Hunting a 16-Year-Old SQLite Bug - Tailscale's writeup of tracking down a WAL reset bug that survived since 2010 is the best debugging read of the week, and a useful reminder that your agent cannot do this for you yet. Read it for the method, not the fix.

  • Claude's System Prompts, Published - Anthropic now publishes the system prompts in release notes. Free lesson in how a production prompt is structured, from people who tune it for a living.

  • Ten Weeks to Understanding Inference Serving - A 30 minutes a day roadmap through LLM inference and optimization, for when your infra bill stops being a rounding error.

  • Build a Nano Coding Agent From Zero - A stripped down agent harness built from scratch, the fastest way to stop treating your coding agent as magic.

🏆 Top on Product Hunt

💬 Builder Conversations

💰 The Money

💎 Hidden Gems

One More Thing...

Five frontier models shipped this week and every one of them arrived with a benchmark table. None of those benchmarks are your product. The builders who will switch models confidently next quarter are the ones who spent an hour this quarter writing down twenty real prompts from their own app, with the answers they want, in a file. That is your eval set. It costs nothing and it is the only number that should decide what you run in production.

Know a builder still picking models off a leaderboard? Forward this along.

Keep shipping,

P.S. Pin your model version in production. "Latest" is a great way to ship a slightly different product every Tuesday.