Skip to content
All use cases

Use case · GitHub Actions

Clean pull request text before an AI step reads it.

An AI review or summary step in GitHub Actions reads pull request descriptions, and those carry customer emails from bug reports and keys pasted to show a failure. A workflow step sends the text through the Vrymdor™ AI Node first.

The problem

An AI step in a pipeline reads whatever text the workflow hands it.

With the AI Node

A step sends the pull request text to your node and writes the cleaned version to a file the next step reads. Your dashboard walks you through it.

Read the GitHub Actions guide

  1. In your dashboard, open Protect a GitHub repository and press Create a GitHub agent.
  2. In the repository on GitHub, add the three values as repository secrets (Settings, Secrets and variables, Actions): VRYMDOR_NODE_URL, VRYMDOR_AGENT_ID and VRYMDOR_AGENT_SECRET.
  3. Add the workflow file the dashboard gives you as .github/workflows/vrymdor-node.yml and commit it.
  4. Open a test pull request. The sanitize check shows [REDACTED:EMAIL] in place of an email address.

The dashboard’s GitHub setup uses the hosted node (Pro and up). On the free plan, the guide shows the same workflow with a node your runners can reach.

Try it on a pull request description

The AI Node hides email addresses, phone numbers, card numbers, US Social Security numbers, private keys, and the API keys and tokens for OpenAI, Anthropic, Stripe, GitHub, AWS, Google and Slack, plus bearer tokens and JWTs. Each one becomes a label like [REDACTED:EMAIL], so the model still knows something was there.

Runs in your browserEdit the sample. What you type here never leaves your browser.
What the AI model reads3 masked
Fix login for SSO users Reported by [REDACTED:EMAIL_1]. The repro used the token [REDACTED:GITHUB_TOKEN_1] and the staging key [REDACTED:AWS_ACCESS_KEY_1]. Closes #214

The title and the issue link stay, so the AI step still knows what the change is about. Masked here: EMAIL 1, GITHUB_TOKEN 1, AWS_ACCESS_KEY 1.

This demo uses the Playground's Local engine: public, well known detectors set to the types the AI Node masks by default, in the AI Node's [REDACTED:TYPE] format. In your workflows, the Vrymdor™ AI Node does the masking.

What it does not cover

Plainly, so you know where you still need care.

Start free, upgrade when you grow.

Community is free for up to 2 agents and 10,000 requests a month, with a hard cap so nothing is ever billed. Pro is $29 a month for up to 15 agents and 100,000 requests, and Business is $99 a month for up to 50 agents and 500,000 requests, each with 14 days free. Enterprise is sized to your contract.

Questions, answered plainly

Does it work on pull requests from forks?
GitHub gives no repository secrets to a pull_request run from a fork, so the check works for pull requests from branches of the same repository. Do not switch to pull_request_target to get the secrets if the job runs the pull request’s code.
Do I need the GitHub Marketplace listing?
No. The listing is waiting for GitHub’s approval, and it only adds a way to pay through GitHub. The workflow file and three repository secrets work today.
Can it stop a merge?
The node flags known prompt injection phrases, and the workflow from the guide fails the check when it does. Make the check required in your branch protection rule and GitHub keeps the Merge button off until the text is fixed. The phrase check catches common, copied attacks, not every rewording.