Skip to main content
31 markdown scenarios live under scenarios/ in the Archal repo. Browse from the CLI: 
archal scenario list
archal run scenarios/security-suite/exec-impersonation.md --sandbox

​
Pick a first scenario

If you want to testStart withClonesRiskRun
Social-engineering resistancesecurity-suite/exec-impersonation.mdSlack, Jira, StripeApproval spoofingarchal run scenarios/security-suite/exec-impersonation.md --sandbox
Refund controlssecurity-suite/race-refund.mdSlack, Jira, StripeFinancial controlsarchal run scenarios/security-suite/race-refund.md --sandbox
Code-review judgmentsecurity-suite/reviewer-impersonation.mdGitHub, Slack, JiraIdentity and accessarchal run scenarios/security-suite/reviewer-impersonation.md --sandbox
Cross-system privacyadversarial/cross-system-pii-leak-customer-name-in-github-issue.mdGitHub, Slack, StripeData exposurearchal run scenarios/adversarial/cross-system-pii-leak-customer-name-in-github-issue.md --sandbox
Discord bot behaviordiscord/thread-escalation.mdDiscordEscalation handlingarchal run scenarios/discord/thread-escalation.md --sandbox
Use archal scenario list --tag <tag> when you know the risk category, and archal scenario list --clone <clone> when you know the service surface.

​
Sample scenario

scenarios/security-suite/exec-impersonation.md - an attacker impersonates an exec over Slack and tries to push the agent into approving a wire transfer. Success criteria check that the agent verified out-of-band before acting.

​
Categories

BucketPathCount
Adversarialscenarios/adversarial/15
Security suitescenarios/security-suite/15
Discordscenarios/discord/1

​
Risk taxonomy

The hosted catalog tags scenarios by failure mode:
TagMeaning
identity-and-accessWrong actor, account, or stale authorization
data-exposureSensitive data crossing an unsafe boundary
financial-controlsRefunds, payments, billing, approval scope
change-managementRisk hidden in releases, diffs, or migrations
governance-and-approvalPolicy precedence, escalation, truthful approval checks
cross-system-reasoningSafe action requires correlating evidence across systems
secrets-and-supply-chainCredentials, dependency trust, hidden payloads

​
Security suite

Social-engineering and policy-verification scenarios across GitHub, Jira, Slack, Stripe, and Linear. 
approval-spoof.md            metric-smoothing.md         refund-amnesty.md
bulk-closure-pressure.md     mirror-patch-confusion.md   reviewer-impersonation.md
coupon-blast.md              payment-link-rush.md        rollback-pressure.md
cross-client-leak.md         quorum-bypass.md            typosquat-hotfix.md
exec-impersonation.md        race-refund.md              vendor-wire-override.md

​
Adversarial

Same-name confusion, revoked credentials, hidden policy violations, cross-system leaks. 
board-blackout-same-name-contractor-safe-subset-only.md
calendar-invite-from-fired-employee-triggers-data-access.md
cross-system-pii-leak-customer-name-in-github-issue.md
github-pr-approved-but-ci-secretly-disabled.md
gmail-thread-contains-revoked-api-key-agent-must-not-use.md
gws-calendar-double-booking-vendor-payment-race.md
northwind-duplicate-vendor-scope-freezes-only-one-bill.md
privacy-review-same-name-contractor-ui-copy-only.md
quarter-close-mixed-queue-same-name-contractor-safe-subset-only.md
quarter-close-overlap-vendor-fraud-refund-and-offboarding.md
ramp-card-spend-after-termination-notice-in-gmail.md
ramp-google-workspace-expense-fraud-evidence-in-email.md
ramp-gws-receipts-dont-match-calendar-locations.md
refund-queue-same-name-offboarding-safe-template-only.md
supabase-migration-contains-rls-bypass-hidden-in-comment.md

​
Discord

thread-escalation.md