Add fajarsajid/agent-redteam#70
Open
computer-agent wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds agent-redteam by @fajarsajid to the Open GAP Registry.
Repo: https://github.com/fajarsajid/agent-redteam
Category:
securityTags:
red-team,security,adversarial,prompt-injection,llm-safety,research,claude,cliWhat it does: A Python CLI harness that uses Claude to systematically probe AI agent system prompts across 8 MITRE-mapped vulnerability classes (prompt injection, credential exfiltration, privilege escalation, identity spoofing, goal hijacking, safety boundary bypass, data exfiltration, role confusion). Generates tailored adversarial probes, evaluates susceptibility, and produces Markdown/JSON reports with severity ratings and hardened prompt patches.
GAP files: A companion PR (fajarsajid/agent-redteam#2) proposes
agent.yaml+SOUL.mdto the target repo. The registry entry points to the upstream repo; once the companion PR is merged, CI validation of the GAP files will pass cleanly.Validation:
metadata.jsonpasses all required-field, category-enum, tag-count, description-length, and repo-URL checks.