AI for Life

Blog

Which repo security scan should you run first?

Featuring From the Weekly Meeting. Published July 29, 2026.

Anthropic’s repo security tool runs in two steps: a manual scan in each repo first, then the background plugin that keeps watch. Frank walks the setup and why /doctor comes first. Codex shipped a security CLI the same morning and GitHub is rolling out its own scanner, so layer them.

Watch the clip

More from the Weekly Meeting

Why do your completed tasks keep coming back from the dead?

  • Michael Wacht

Michael's completed tasks kept resurrecting because Obsidian stores files, and files have no state. He wired Todoist's free tier into Cowork through the API and the zombie task list died in an afternoon. His line for it: quantum entanglement for to-do lists.

Why rebuild a to-do list the market already perfected?

  • Michael Wacht

Why build a to-do list when one already exists that just needs seamless integration? Michael names the builder's trap: making tools the market already perfected while avoiding the real work. His honest version: everybody's hiding out from cold calls and sales. That's why we build.

Most people start building with AI too fast. Here's the habit that fixes that.

  • Mike Thomson

Mike Thomson shares a practical method that consistently produces better AI-built projects: write a project brief first, then use "planning mode" before you touch a single tool.

Community

Keep going with AI for Life

This clip comes from the AI for Life Weekly Meeting, live Wednesdays at 11 a.m. Eastern. Join the community to be in the room for the next one.

Join the AI for Life community (opens in a new tab, leaves this site) Request a custom lesson