ShadowAgent Guard
Your AI coding agent obeys files in the repo. Attackers can write those files.
One pull request can slip in a hallucinated package, an invisible instruction in AGENTS.md, an auto-approved shell tool, or a deleted test. ShadowAgent Guard diffs every PR, grades it A to F and blocks the merge before an agent or a developer runs any of it.
- uses: Ahmadbey678/ShadowAgent-Guard@main
Hidden-Unicode rules injection
What humans see vs. what the agent sees
The same AGENTS.md from the demo pull request. Unicode tag characters render as nothing in GitHub's diff view and in editors, but the model reads them as plain text.
Same PR, before and after remediation
From BLOCK to PASS
Both reports below are real report.json files produced by scanning the demo repository's ai-pr and ai-pr-remediated branches. Remediation used IBM Bob's hardened agent configs plus manual fixes for the dependencies and tests. The tool reports those two categories; it does not fix them automatically.
Hardening, generated by IBM Bob
Risky config vs. hardened config
The shadowagent-guard Bob mode can only write to guard-out/, so it proposes hardened files rather than editing the target repo. A human applies them.
How it works
From pull request to merge gate
Findings
Findings
Threat model
How each attack works
Measured on the demo repo
Impact
| Planted issue | File | Rule | Caught |
|---|
Your own scan
Load a report.json
or drag and drop it anywhere on this page.
Privacy: Reports are rendered in your browser and never uploaded.