AI coding stack converges (OpenSpec, ECC, Kiro) as CI-targeting npm worm raises guardrails stakes
AI coding tools are consolidating around config-as-code and multi-agent support (OpenSpec, ECC, AWS Kiro) while a new npm worm targeting CI and AI toolchains demands tighter supply-chain controls. OpenSpec’s latest release adds profile-based installs, auto-detection of existing AI tools, and first-class support for Pi and AWS Kiro, streamlining how teams standardize assistant skills across repos ([v1.2.0 notes](https://github.com/Fission-AI/OpenSpec/releases/tag/v1.2.0)). In parallel, Everything Claude Code’s “Codex Edition” unifies Claude Code, Cursor, OpenCode, and OpenAI Codex from a single config, ships 7 new repo-analysis skills, and bakes in AgentShield security tests, plus a GitHub app for org-wide rollout ([v1.6.0 notes](https://github.com/affaan-m/everything-claude-code/releases/tag/v1.6.0)). AWS is pushing Kiro’s agentic coding further to improve code quality ([DevOps.com](https://devops.com/aws-extends-agentic-ai-capabilities-of-kiro-developer-tool-to-improve-code-quality/)), with practitioners showing Kiro CLI working alongside Xcode MCP to ship an iOS app in hours—an example of assistant+IDE workflows entering the mainstream ([DEV post](https://dev.to/aws-heroes/i-promised-an-ios-app-kiro-cli-and-xcode-mcp-built-it-in-hours-519l)). Against this momentum, researchers warn of a new npm worm that can harvest secrets and weaponize CI while spreading via AI coding tools, reinforcing the need for deterministic builds, scoped tokens, and pre-commit/CI policy gates ([InfoWorld](https://www.infoworld.com/article/4136478/new-npm-worm-hits-ci-pipelines-and-ai-coding-tools.html)).