Skip to content

Instantly share code, notes, and snippets.

@solar-flare99
solar-flare99 / security-best-practice.md
Created June 17, 2026 02:57
AI Security and Governance and how to make your coding agents write secure code

To trust an agent moving at this speed, we can’t be the ones checking its work. By the time we’ve read one command, it has already run three more. So the checking has to happen on its own, in the moment, on every single action. Security already has a name for that idea, which is zero trust. We stop assuming something is safe because of who is asking, and we judge each action on its own merits, every time.

It turns out our own bodies already run this exact playbook. The immune system never asks a threat for its credentials or waves it through on reputation. It watches what is happening in front of it, and it shuts the harmful thing down before it can spread. That is the layer we set out to build for AI agents, which is why we named it immunity. Like its namesake, it watches the three places an agent can hurt us: what it does, what it installs, and what it leaves broken behind.

immunity-agent is the open-source guard that does the watching, and it slots into m

@solar-flare99
solar-flare99 / yolo-safely.md
Last active June 9, 2026 02:11
`--dangerously-skip-permissions` Is Fine, Actually

--dangerously-skip-permissions Is Fine, Actually

Coding agents interrupt you constantly. Allow this command? Edit this file? Run this script? Those prompts exist for good reason, but they also make autonomous workflows basically impossible. A multi-hour refactor, a CI pipeline, an overnight agent run: you can't approve every step. So developers turn the prompts off.

That's a reasonable call. But it removes the only checkpoint between your agent and your filesystem, credentials, and network. Immunity Agent puts that checkpoint back, at the agent layer, without getting in your way.

Autonomy Settings by Agent

Agent Flag / Setting Description