Security for AI agents : Block dangerous commands, prevent secret leaks, and enforce runtime policies across Claude,...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Reasonable to try, but it will take more than a quick skim to get real signal.
GitHub health 37/100. no security policy. 6 open issues make this testable, but not something to trust blind.
AI Agent
Multiple
Model
Claude
Build Time
Instant
Fastest way to find out if immunity-agent belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/PrismorSec/immunity-agent ~/.claude/agents/immunity-agentRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/agents/immunity-agentNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ immunity-agent/ ← installs here └─ settings.json
Security for AI agents : Block dangerous commands, prevent secret leaks, and enforce runtime policies across Claude, OpenClaw, Hermes, Antigravity, Codex, Cursor and Windsurf