Sentinel Core – A zero-telemetry enforcement gate for GitHub Actions
Hard-fail CI gate for GitHub Actions, but broader tools like Snyk, TruffleHog already integrate Actions scanning.

External admission gate for GitHub Actions stops AI agents before they execute.
DevSecOps teams, Platform Engineering leads managing AI agents
OPA · GitHub Environments · StepSecurity
the workflow that wants to execute should not be the same place that decides whether execution may continue.
This project puts an external allow/deny boundary before action.
Public entry points:
* live pilot * commercial request * private deployment
There is also a GitHub Marketplace action install surface, but the main point is the boundary model itself: decision stays outside the workflow that is asking to proceed.
Looking for feedback from people working on CI/CD, security controls, approval boundaries, and automated execution.
Hard-fail CI gate for GitHub Actions, but broader tools like Snyk, TruffleHog already integrate Actions scanning.
Replaying past sessions against stricter policies beats guessing rules before you know the risks.
Deterministic agent governance with capability tokens beats probabilistic guardrails.
HTTP proxy mode needs one env var — no SDK required for existing agents.
Fail-closed guardrails for LLM actions with cryptographic approval and audit chains.
The idea of inserting a deterministic 'gate' between proposed tool calls and execution is smart and practical: precomputed classification plus an agent-unreachable vault means destructive operations become reversible by default. The README calls out clear mechanics (envelope checks, vault backup, tiered responses and structured denials) which suggests this is more than a thought experiment — it's a focused infra piece for teams that actually let agents touch production.