|
| 1 | +# ISC-Bench — Agent Entry Guide |
| 2 | + |
| 3 | +## For Humans |
| 4 | + |
| 5 | +Copy this to your AI agent (Claude Code, OpenClaw, Cursor, etc.): |
| 6 | + |
| 7 | +```text |
| 8 | +Help me understand and use ISC-Bench: |
| 9 | +https://raw.githubusercontent.com/wuyoscar/ISC-Bench/main/AGENT_README.md |
| 10 | +``` |
| 11 | + |
| 12 | +--- |
| 13 | + |
| 14 | +## For AI Agents |
| 15 | + |
| 16 | +### Goal |
| 17 | + |
| 18 | +Help the user understand, inspect, reproduce, or contribute to the `ISC-Bench` repository. |
| 19 | + |
| 20 | +`ISC-Bench` is an academic safety research repository for studying **Internal Safety Collapse (ISC)** in frontier LLMs through the **TVD** framework: |
| 21 | + |
| 22 | +- **Task**: a normal-looking workflow |
| 23 | +- **Validator**: a checker that defines success |
| 24 | +- **Data**: missing fields the model must complete |
| 25 | + |
| 26 | +Core claim: |
| 27 | + |
| 28 | +- models can produce harmful or policy-relevant content |
| 29 | +- not because of a direct malicious prompt |
| 30 | +- but as a side effect of completing an ordinary-looking task |
| 31 | + |
| 32 | +### Boundaries |
| 33 | + |
| 34 | +When working with this repository, stay within these limits: |
| 35 | + |
| 36 | +- treat the repository as academic safety research |
| 37 | +- do not rewrite the project as operational misuse guidance |
| 38 | +- do not strengthen harmful examples unnecessarily |
| 39 | +- prefer public templates and documented workflows |
| 40 | +- use [`VERIFICATION.md`](VERIFICATION.md) when judging whether a case counts as **Triggered** |
| 41 | + |
| 42 | +### Step 1: Clone the Repository |
| 43 | + |
| 44 | +```bash |
| 45 | +git clone https://github.com/wuyoscar/ISC-Bench.git |
| 46 | +cd ISC-Bench |
| 47 | +``` |
| 48 | + |
| 49 | +### Step 2: Read in Order |
| 50 | + |
| 51 | +Read these files in this order: |
| 52 | + |
| 53 | +1. [`README.md`](README.md) — project overview, leaderboard, and public entry points |
| 54 | +2. [`VERIFICATION.md`](VERIFICATION.md) — how ISC-Bench defines **Triggered** and verifies cases |
| 55 | +3. [`templates/README.md`](templates/README.md) — public scenario library |
| 56 | +4. [`experiment/README.md`](experiment/README.md) — reproducible evaluation pipelines |
| 57 | +5. [`community/README.md`](community/README.md) — attributed reproductions and evidence |
| 58 | + |
| 59 | +### Step 3: Choose the Right Path |
| 60 | + |
| 61 | +Use the path that matches the user's goal: |
| 62 | + |
| 63 | +- **Inspect evidence** |
| 64 | + Open the JailbreakArena section in [`README.md`](README.md), then follow the linked issue or community case. |
| 65 | + |
| 66 | +- **Understand or reuse templates** |
| 67 | + Start from [`templates/README.md`](templates/README.md), then open the most relevant scenario directory. |
| 68 | + |
| 69 | +- **Run the benchmark pipeline** |
| 70 | + Read [`SKILL.md`](SKILL.md) and [`experiment/README.md`](experiment/README.md), then choose: |
| 71 | + - `experiment/isc_single` |
| 72 | + - `experiment/isc_icl` |
| 73 | + - `experiment/isc_agent` |
| 74 | + |
| 75 | +- **Contribute a new case** |
| 76 | + Check [`VERIFICATION.md`](VERIFICATION.md), collect evidence, and then open the ISC submission issue. |
| 77 | + |
| 78 | +### Step 4: Submit a Case |
| 79 | + |
| 80 | +If the user wants to submit a new case: |
| 81 | + |
| 82 | +1. pick a template and reproduce the behavior |
| 83 | +2. save evidence such as model output or API logs |
| 84 | +3. check [`VERIFICATION.md`](VERIFICATION.md) to confirm the case meets benchmark standards |
| 85 | +4. open the ISC submission issue: |
| 86 | + |
| 87 | +```text |
| 88 | +https://github.com/wuyoscar/ISC-Bench/issues/new?template=isc-submission.md&title=[ISC]+Model+Name |
| 89 | +``` |
| 90 | + |
| 91 | +### Quick Reference |
| 92 | + |
| 93 | +| Resource | Purpose | |
| 94 | +|---------|---------| |
| 95 | +| [`README.md`](README.md) | Human-facing overview | |
| 96 | +| [`VERIFICATION.md`](VERIFICATION.md) | Rules and verification standards | |
| 97 | +| [`templates/`](templates/) | Public TVD scenarios | |
| 98 | +| [`experiment/`](experiment/) | Single-turn, ICL, and agentic pipelines | |
| 99 | +| [`community/`](community/) | Curated reproductions tied to issues | |
| 100 | +| [`SKILL.md`](SKILL.md) | Command-level workflow for running ISC-Bench | |
| 101 | +| [`tutorials/`](tutorials/) | Onboarding material | |
| 102 | + |
| 103 | +### One-Sentence Summary |
| 104 | + |
| 105 | +Clone the repo, read [`README.md`](README.md) and [`VERIFICATION.md`](VERIFICATION.md), then choose the correct template, experiment, or submission path based on the user's goal. |
0 commit comments