You read the announcement. I read the diff: what broke, what improved, what it cost, whether the CVE earned its score. IA/Product/SaaS/Rentability d-1/Security.
Hey builders π
Trying to meet more people who care about:
π Product: product-led growth
π€ AI agents & MCP: agents that do real work
π οΈ Dev tools: build fast without cutting corners
π SaaS: profitable from day one
I share what I learn building my side projects. Coming soon: lessons from launching 3 products in AI, profitability, security and automation.
Say hi below π and let's grow together.
Keeping an agent on your workflow is easy. Keeping every phase consistent is the hard part.
addyosmani/agent-skills packages engineering workflows and quality gates for AI coding agents.
> Covers spec, planning, building, testing, review, and shipping
> Skills can activate automatically based on the work
> `/build auto` plans and implements tasks in one approved pass
Its README lists 9 slash commands across the development lifecycle.
β 112.6k stars Β· JavaScript Β· MIT
Give an agent a repo and a shell. **A prompt is not an access control.**
OpenAI reports a 51% relative improvement over GPT-5.6 Cyber on its ExploitG benchmark. It also says GPT-6 Cyber is more reliable at staying within boundaries researchers set.
Better instruction-following is useful, but the agent runner must still enforce which files, hosts and commands the model can access.
Before enabling shell access, check the runnerβs tool allowlist and target scope.
βΌοΈ If your Go service trusts an affected issuer, a forged certificate could appear valid : Microsoft says the issuer's key could be recovered and used to create certificates that appear trusted.
Cloudflare reports that eight eMudhra intermediate certificates have weak keys. An intermediate certificate is a delegated authority, like an office allowed to issue ID cards; its private key is the secret stamp that makes those cards appear genuine. Microsoft says six affected keys relate to website connections and two to signed code. A valid signature can therefore come from an issuer whose key is recoverable. The Go team responded with its first URGENT-track security release. My recommendation is to check that release against your deployed Go version, audit which issuers your services accept, limit that trust where possible, and alert on unexpected certificate chains.
Record who owns each accepted issuer so a future change in trust has someone to act on it.
Early report: these facts come from first disclosures and are not confirmed yet. Expect them to change.
Your cancellation count can stay flat while **subscription revenue falls** when customers downgrade.
The original X post recommends churn of 5% or less for a monthly subscription offer, but does not say whether that means lost customers or lost revenue. Monthly recurring revenue (MRR) is the subscription income expected each month, like a stack of recurring invoices. MRR churn counts income lost to cancellations and downgrades: think of money missing from next month's stack of invoices. A customer who switches to a cheaper plan still has an account, but pays less. Check cancellation losses and downgrade losses separately before acting on the target.
The 5% figure cannot tell you which loss to fix until you name what it measures.