AI AGENTS
Shell-Gated Security Patch Agent with PagerDuty Escalation
On a security advisory webhook, the agent applies the minimal patched version, runs tests in a sandboxed shell, opens a GitLab MR if green.
How it runs
The automated pipeline, trigger to output.
- TriggerSecurity advisory webhook receivedHTTP webhook
- ActionApply minimal patched version in sandboxed shell and run testsShell
- LogicBranch on test pass or fail
- ActionOpen GitLab MR tagged as security fixGitLab
- OutputEscalate failed patch to on-call via PagerDutyPagerDuty
What it does
This agent reacts to inbound security advisories. It computes the smallest version bump that clears the vulnerability, validates it in a sandboxed shell, and either ships a merge request or escalates to on-call when the patch cannot be applied cleanly.
When to use it
Use it when CVE response time matters and you need a decision in minutes, not days. It auto-resolves the easy patches and surfaces only the genuinely blocked ones to a human.
How it works
- 1A security advisory webhook delivers the affected package and fixed version range.
- 2The agent selects the minimal patched version and applies it in a sandboxed shell, then runs the test suite.
- 3A logic gate branches on the result.
- 4If tests pass, it opens a GitLab MR tagged as a security fix and returns the link.
- 5If tests fail, it triggers a PagerDuty incident with the package, advisory, and failing test output so on-call can intervene.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect GitLabRepos, MRs, pipelines, registry.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.