Submission: agi_loop (Security Arena scenarios + artifacts) #24
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
Author
|
Team: agi_loop Location: scenarios/security_arena/submissions/agi_loop/ Scenarios: (lista) Evidence: baseline_passed.json, attack_succeeded.json incluidos por escenario Run instructions: refer to per-scenario README |
Author
|
I opened a clean submission-only PR (envío/agi_loop-clean) that merges cleanly and contains only scenarios/security_arena/submissions/agi_loop/**. Please review the clean PR instead; #24 includes additional framework-wide changes. |
Author
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.
Team: agi_loop
Scope: Security Arena submissions under scenarios/security_arena/submissions/agi_loop/
Scenarios included: SearchPoison, NPM-Nightmare, ApiKeyAlchemist, HumanHandoffHack, HRHack, ContractKiller
Evidence: Each scenario includes test_results/baseline_passed.json and test_results/attack_succeeded.json where applicable.
Repro: Code + assets + tests included; run instructions in per-scenario README files.