Astra의 보안 분류·Agent Plugins 표준·Claude Code 권한 자동화

After evaluating one of our upcoming models, Astra, we're treating it as our first "critical" model for cybersecurity under our Preparedness Framework. This is a scenario we've planned for, and we're putting additional controls in place to ensure Astra's further development

Google, Microsoft, OpenAI, Cursor, and Vercel just standardized how to package MCP and skills as a plugin for AI Agents. write a skill once and every one of them can now load it. there are two ways to give a coding agent new abilities today. a skill is a folder of written instructions the agent reads when it needs them, and an MCP server is a small program that connects the agent to a tool, an API, or a database. both already work across agents. what has never worked across agents is the package you ship them in. every tool picked its own folder names, its own settings file, and its own place to put things. so the same skill gets rearranged for Cursor, again for Copilot, again for Codex, and the copies slowly stop matching. the fix published yesterday is called Agent Plugins 1.0.0, and it standardizes that wrapper and nothing else. a plugin is a folder with a file called plugin.json at the top, skills inside a folder named skills, and MCP servers listed in a file named mcp.json. the settings file names the plugin and nothing more. it cannot point somewhere else or hide the pieces inside itself, so every tool looks in the same three places and there is nothing to configure. anything a single tool wants to add goes into its own clearly named folder that other tools skip over. that keeps the shared part small enough that everyone can agree on it. the pieces also fail separately, so a broken MCP server does not stop the skills sitting next to it from loading. what the standard leaves out is worth knowing. it says nothing about how plugins get installed, what they can touch once running, or how to check who wrote one, and it gives passwords and API keys nowhere safe to live. a plugin is still a folder of code that runs on your machine. spec: https:// agent-plugins.org/specification the name missing from all of this is Anthropic. skills and MCP both came from there, and Claude Code has packaged plugins in almost exactly this shape since 2025. Anthropic is not on the group steering the standard, and Claude Code is not on the list of tools supporting it, which is ChatGPT and Codex, Cursor, GitHub Copilot, Kiro, and VS Code. Google joined as a maintainer on launch day, and its Agents CLI is one of the first two Google products already shipping in this format. I wrote a full walkthrough of that tool, which is the clearest picture of what a plugin actually does once it reaches an agent. it covers how Agents CLI drops Google's agent-building skills into Claude Code, Cursor, Codex, or Antigravity, then builds a citation-grounded RAG agent, runs a 20-scenario eval suite that catches a hallucination, traces it back to a single line in the system instruction, and deploys the fixed agent. quoted below.

ClaudeDevs

@ClaudeDevs

Starting August 14, auto mode will be the default permission mode in Claude Code for Pro, Max, and Team users. Auto mode reviews shell commands and actions with a separate classifier. In testing, it caught 89% of dangerous commands. Manual approval caught 14%.