A preprint submitted to arXiv on September 7, 2026, "Scanning the Harness: An Empirical Study of Supply-Chain Defects in AI Coding-Agent Configurations," scanned 3,171 public GitHub repositories and found a security defect in 16.0% of the agent setups it examined, with 16.7% carrying a confirmed defect of any kind. The corpus covers Claude Code, Cursor, GitHub Copilot and OpenAI Codex. It carries no peer review.
The breakdown is where the work is. 2,660 setups assemble two or more component types, 511 are published skill collections. 9.8% of setups pin no version on the MCP server they install. 3.1% ship a scoped-looking grant that actually pre-approves arbitrary execution, and 3.8% ship a skill that pre-approves the shell for anyone who installs it.
That is a dependency layer with no lockfile and no install-time check, and it runs with your privileges as soon as you install it. One methodological finding deserves repeating: the raw scanner flagged 25.5% on the same rules, so unaudited analyzer output inflates findings by a wide margin, and the paper found no confirmed credential-exfiltration path.
Grep your repositories for an unpinned npx -y @scope/server-name in MCP declarations and pin the version, then audit any skill or hook that pre-approves shell commands for whoever installs it. Treat a rate from a raw analyzer as a property of the analyzer until someone re-derives the findings.