Skip to main content

security-claim-agentdojo

A superred SecurityClaim package paired with agentdojo-target. Three composable layers:

  1. Layer 1: original AgentDojo injection tasks. One paired Task per canonical (user_task, injection_task) pair, 27 tasks total across the four AgentDojo suites (banking, workspace, slack, travel). Subdivided by attack-semantic category per the table the user confirmed. Benchmark version pinned to the latest released (v1.2.2) via the target's seed_loader.BENCHMARK_VERSION.
  2. Layer 2: bespoke system-purpose-violation goals. Standalone goals tailored to the composite multi-suite agent. Deterministic security predicates, NOT LLM-as-judge. Each task carries a benign user prompt; the attacker chooses delivery based on scope.
  3. Layer 3: combined. Composition of Layers 1 and 2.

Install

# from the superred-modules repo root
pip install -e ./targets/agentdojo
pip install -e ./security_claims/agentdojo

Quick start

from agentdojo_target import AgentDojoTarget
from agentdojo_claim import agentdojo_layer1_claim
from superred.core.controller import Controller, TargetFactory

target_factory = TargetFactory(
    create=lambda: AgentDojoTarget(
        pipeline_model="openai/gpt-4o-2024-05-13",
        api_base=BASE, api_key=KEY,
    ),
    concurrency=1,
)
claim = agentdojo_layer1_claim()  # all 27 canonical pairs

controller = Controller(
    optimizer_factory=lambda: MyOptimizer(),
    target_factory=target_factory,
    security_claim=claim,
    scope=frozenset({USER_TAG, TOOLS_TAG}),  # example scope
)
await controller.run()

See ASSUMPTIONS.md for divergences from AgentDojo upstream and Layer-2 design rationale.

Status

v0.1.0 alpha. Public surface is unstable.

Credits / upstream

This package's source is original superred work (MIT, Copyright (c) 2026 Simon Sure). It bundles no third-party code or data.

Layer 1 adapts the AgentDojo benchmark (Debenedetti et al., 2024; MIT, Copyright (c) 2024 Edoardo Debenedetti, Jie Zhang, Mislav Balunovic, Luca Beurer-Kellner, Marc Fischer, and Florian Tramèr). AgentDojo is a runtime dependency (agentdojo>=0.1.35), installed from PyPI and not redistributed here; its injection/user tasks are run and scored via superred's agentdojo-target. Please cite AgentDojo when reporting Layer-1 results.

Layer 2 goals are bespoke, hand-authored superred content (deterministic security predicates, not derived from AgentDojo's tasks). See ASSUMPTIONS.md.

Metadata

Release files for superred-claim-agentdojo 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for superred-claim-agentdojo 0.1.0
File Size Uploaded
superred_claim_agentdojo-0.1.0.tar.gz 53.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for superred-claim-agentdojo 0.1.0
File Interpreter ABI Platform
superred_claim_agentdojo-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 99.5 kB

Release files / superred_claim_agentdojo-0.1.0.tar.gz

Download URL superred_claim_agentdojo-0.1.0.tar.gz
Size 53.1 kB
Tags Source
SHA-256 checksum
How to use checksums
fc93c748f99fa586ec77e59426df4a9b2da0a81f634ed0f22f53fa6f8c35eda5
BLAKE2b-256 checksum
How to use checksums
a157df33a3aef4ec2b30b45006485e7af133c111ba6cd4d6565098c2fc0c794b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 22, 2026.

Transparency log

Release files / superred_claim_agentdojo-0.1.0-py3-none-any.whl

Download URL superred_claim_agentdojo-0.1.0-py3-none-any.whl
Size 46.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0eb90b3d56ff451c8b21472b38dacc0d080eec9ad47cf81803c191f5f323f69c
BLAKE2b-256 checksum
How to use checksums
6a79a08888555d6a4da3cf92796589e31a33abd2205b2aad83cdf1ba7f0fcd60
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 22, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page