Prefixing Functions with ‘secure_’ Leads Agents to Write Safer Code
Researchers gave coding agents a three‑step API build task and varied the prefix on initial function names (secure_, safe_, energetic_, etc.). Only the secure_ prefix consistently caused agents to add password fields and hash them with bcrypt, showing a simple naming tweak can steer agents toward more secure implementations.