Agents Week 2026 made the agent stack legible: Security and MCP, Agent Memory, Sandboxes, and Artifacts. If your skills do not map cleanly to those four layers, you are building blind.
Cloudflare just turned a year of fuzzy agent talk into a clear blueprint. Their Agents Week recap (linked below) lines up the agent stack into four pillars: Security and MCP, Agent Memory, Sandboxes, and Artifacts. That is not marketing. It is a working map for anyone shipping agent skills today, and it is the cleanest way to audit your own stack before the next ten skills get bolted on.
Why these four, and why now
Cloudflare did not invent these categories. Builders have been improvising around them for a year. What changed this week is that a hyperscaler shipped real primitives for each one on the same day, with the same vocabulary. That is the moment a fuzzy idea becomes a category.
Security and MCP got Mesh, Managed OAuth for Access, scannable tokens, and a reference architecture for governing MCP at the enterprise layer. Agent Memory shipped as a managed service for persistent recall and forgetting. Sandboxes went GA with real shells, filesystems, and background processes. Artifacts launched as Git-compatible versioned storage that any agent can fork, write to, and hand off by URL.
Read together, those four launches are not a feature list. They are the blueprint that every serious skill stack will be measured against from here on.
A skill block to map your stack against the 4 pillars
---
name: stack-mapper
version: 0.1.0
description: Map an agent's current skills and tools against the Cloudflare 4-pillar blueprint
---
# Stack Mapper
Use this when the user wants to audit an agent stack, plan a new skill, or
benchmark their setup against modern agent infrastructure.
## The 4 pillars
1. Security / MCP — identity, scoped tokens, guarded tool access, MCP governance
2. Agent Memory — durable state, recall, forgetting, cross-session continuity
3. Sandboxes — isolated compute for code, shell, and untrusted output
4. Artifacts — versioned storage for code, files, and handoff outputs
## Workflow
1. List every active skill and tool the agent uses today
2. Tag each one with its pillar (or "missing")
3. Save the audit to memory/stack-audit-YYYY-MM-DD.md
4. For each empty pillar, propose the smallest skill that closes the gap
5. Flag any skill that touches more than one pillar without scoping
## Output rules
- One pillar per skill where possible
- Note credentials, scopes, and storage paths explicitly
- Mark anything that runs untrusted code as Sandbox-required
- Treat memory writes as infrastructure, not chat decoration
What this means for skill builders
Most agent stacks today are heavy on tools and light on structure. There are ten skills for content generation, one half-wired memory note, no sandbox at all, and credentials sitting in plain text. That worked while the field was young. It will not survive the next twelve months.
The four pillars give you a forcing function. Map every skill you ship to a pillar. Anything that does not fit is either redundant, miscategorized, or filling a gap you should solve with infrastructure instead of a prompt.
What to do this week
Run the audit. Open your skill directory, label each one against the four pillars, and save the result. Empty pillars are not a failure; they are the shortlist for the next skills you build.
Then read the Cloudflare recap with one question in mind: which of these primitives could replace something I am currently faking with a prompt? Every honest answer is a leverage point. Source: https://blog.cloudflare.com/agents-week-in-review/
The agentic cloud is no longer a slide. It is a four-pillar stack with shipping products behind each layer. Builders who design their skills to fit that map will compound. Builders who keep stacking prompts on top of one another will keep shipping fragile demos.