A coding-agent guardrail that checks 67 security gates before the model writes code
ZyOffsec · reddit · 2026-07-21
The author argues that most coding-agent guardrails fail because they run after code is written, which catches bad lines but misses omissions like missing rate limits, audit logs, or ownership checks.
- Their solution moves constraints into the write path.
- The skill can be loaded into Claude Code, Cursor, or Codex.
- Before emitting code, it checks the touched surfaces against 67 numbered gates covering injection, secrets, authorization, input validation, crypto, and logging.
- If something fails, it revises the output before writing it.
- It triages itself away on non-security work, so ordinary edits are mostly unaffected.
- The project is free, MIT-licensed, and has no telemetry.
The post ends by asking whether others constrain the agent in-loop or rely on post hoc review.
More from coding & agent
- GPT-6 Astra beats Factorio with enemies in 44 in-game hours at ~$4,500 API cost — liminal_bardo · 2026-09-11
- Investment Analyst Asks How to Build a Claude-Based Diligence Agent Stack — Careless_Tie2286 · 2026-09-11
- How Do You Catch Behavioral Regressions in LLM Agents Between Releases? — Beautiful_Belt_601 · 2026-09-11
- Treating agents like 50 First Dates: a 3-layer context system so every conversation doesn't start from zero — evielync · 2026-09-11
- Running the Firefox MCP on Android via Termux, ngrok, and mcp-proxy — Nervous-Strain7544 · 2026-09-11
- SmolVM open-sources persistent computer infrastructure for agents that outlive chat sessions — aniketmaurya · 2026-09-11