SECOPS
SRI Hash PR Gate for New Scripts
On every pull request, scans changed HTML and templates for external <script> tags missing or mismatching Subresource Integrity hashes and blocks the merge with an inline GitHub…
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub pull request opened or synchronizedGitHub
- ActionParse changed files for external script/link tagsGitHub
- LogicValidate SRI present and hash matches fetched resource
- OutputSet commit status and comment violations on PRGitHub
What it does
This workflow enforces Subresource Integrity at code-review time. When a pull request is opened or updated, it inspects the diff for any external `<script>` or `<link rel=stylesheet>` referencing a third-party origin. If a tag is added without an `integrity` attribute, or its declared hash does not match the actual fetched resource, the workflow fails a GitHub status check and comments the offending lines so the supply-chain risk never reaches production.
When to use it
Use it as a merge gate on any frontend repo that pulls scripts from CDNs or vendor domains. It turns SRI from a best-practice nobody remembers into an enforced contract on every PR.
How it works
- 1A GitHub pull_request event triggers the run.
- 2The changed files are pulled and parsed for external script and style tags.
- 3For tags with an SRI hash, the resource is fetched and re-hashed to confirm a match; tags without one are flagged.
- 4A logic step decides pass or fail based on missing or mismatched hashes.
- 5The result is written back as a GitHub commit status plus an inline review comment on each violation.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More SecOps workflows
Compile a weekly WAF tuning review with trends to Confluence
Every week an agent rolls up Cloudflare WAF block clusters by rule and ASN, compares them to prior weeks for trend direction.
Sensitive Dropbox Link Owner Remediation Loop
When a newly created Dropbox shared link points to a sensitive file, this workflow DMs the file owner, gives them a deadline to justify or revoke it.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
Page on-call when a WAF rule mass-blocks legitimate traffic
On demand or every few minutes, it detects a single Cloudflare WAF rule suddenly blocking a broad spread of ASNs and paths (a likely false-positive storm).
PII Content Scan on New Dropbox External Share
When a file gets an external Dropbox link, it reads the file content, uses an AI classifier to detect PII or secrets.
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.