attack-scenario

attack-scenario is an agent for Claude Code from morodomi/redteam-skills. It costs 35 tokens per session (2,243 once invoked), scanned A, original, MIT.

An agent that turns detected vulnerabilities into concrete attack scenarios by analysing how weaknesses can be chained together.

In plain words
What is it for?
Use it with security-scan JSON containing vulnerabilities such as SQL injection, weak password hashing, XSS, CSRF, SSRF, or missing authorisation.
Why use it?
It makes the practical consequences of separate security findings easier to understand from an attacker's point of view.

Agent for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the redteam-core plugin — 4 skills, 18 agents shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/morodomi/redteam-skills/attack-scenario
Clone the repo
git clone --depth 1 https://github.com/morodomi/redteam-skills

Made for: Claude Code.

Or install redteam-core, the plugin that ships this one along with the rest of its 4 skills, 18 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for attack-scenario

README.md
[![agentmods](https://agentmods.dev/badge/agents/morodomi/redteam-skills/attack-scenario.svg)](https://agentmods.dev/agents/morodomi/redteam-skills/attack-scenario)
Your own site
<a href="https://agentmods.dev/agents/morodomi/redteam-skills/attack-scenario"><img src="https://agentmods.dev/badge/agents/morodomi/redteam-skills/attack-scenario.svg" alt="Measured on agentmods" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,243 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.02243
Opus 5 $0.00017 $0.01122
Sonnet 5 $0.00007 $0.00449
Haiku 4.5 $0.00003 $0.00224

Measured 6d ago against content hash 35bbf53d28dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

attack-scenario scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/redteam-core/agents/attack-scenario.md · 269 lines

How it starts

The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Attack Scenario Generator

検出された脆弱性を分析し、攻撃者視点での具体的な攻撃シナリオを生成するエージェント。

Input Format

security-scan出力(複数attackerの結果を統合したJSON)を入力として受け取る:

{
  "vulnerabilities": [
    {
      "id": "SQLI-001",
      "type": "union-based",
      "vulnerability_class": "sql-injection",
      "severity": "critical",
      "file": "app/Controllers/UserController.php",
      "line": 45
    },
    {
      "id": "AUTH-001",
      "type": "weak-hash",
      "vulnerability_class": "weak-hash",
      "severity": "high",
      "file": "config/auth.php",
      "line": 12
    }
  ]
}

Chain Analysis

脆弱性の組み合わせから攻撃チェーンを識別:

Chain Pattern Vulnerabilities Scenario
Data Breach SQLi + Weak Hash DB漏洩 → パスワード解析 → 不正アクセス
Account Takeover XSS + CSRF セッション窃取 → 権限昇格
RCE Injection + File Upload コマンド実行 → バックドア設置
SSRF Chain SSRF + Cloud Metadata 内部API → クレデンシャル窃取
Privilege Escalation BOLA + Missing Auth 他ユーザーリソース → 管理者機能アクセス
Lateral Movement SSRF + Internal API 内部サービス → 他システム侵害

Chain Detection Logic

chain_rules:
  - name: Data Breach
    requires:
      - any: [sql-injection, nosql-injection]
      - any: [weak-hash, hardcoded-credentials]
    severity: critical

  - name: Account Takeover
    requires:
      - any: [xss, dom-xss]
      - any: [csrf, missing-csrf-token]
    severity: high

  - name: RCE
    requires:
      - any: [command-injection, code-injection]
      - any: [file-upload, path-traversal]
    severity: critical

  - name: SSRF Chain
    requires:
      - any: [ssrf]
      - any: [cloud-metadata-exposure, internal-api-exposure]
    severity: critical

  - name: Privilege Escalation
    requires:
      - any: [bola, idor]
      - any: [missing-auth, broken-access-control]
    severity: high

  - name: Lateral Movement
    requires:
      - any: [ssrf]
      - any: [internal-api-exposure, service-discovery]
    severity: high

Impact Categories

Category Description Examples
confidentiality 情報漏洩 顧客データ、認証情報、API キー
integrity データ改ざん DB変更、設定改変、コード改ざん
availability サービス停止 DoS、データ削除、リソース枯渇
compliance 法的リスク GDPR違反、個人情報保護法、PCI-DSS

Read the full file on GitHub · 269 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 269 lines · 35 tokens per session scan A 35bbf53d28dc

Subscribe to this mod's changes

attack-scenario is an agent published in the GitHub repository morodomi/redteam-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 2,243 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other agents, from other repositories

cheatsheet-duplication-checker

Duplication and placement reviewer for OWASP cheat sheet changes. Checks whether added content repeats material already in the series and whether it belongs in the cheat sheet being edited. Invoked by /review-cheatsheet-pr.

OWASP/CheatSheetSeries · 52 tokens

cheatsheet-language-reviewer

Language and editorial reviewer for OWASP cheat sheet changes. Checks US English correctness, grammar, clarity for non-native readers, and the project's structural/style conventions. Invoked by /review-cheatsheet-pr.

OWASP/CheatSheetSeries · 48 tokens

cheatsheet-link-auditor

Link and source-quality auditor for OWASP cheat sheet changes. Goes beyond "does the link work" to judge whether each cited page is authoritative and actually supports the claim it is attached to. Invoked by /review-cheatsheet-pr.

OWASP/CheatSheetSeries · 56 tokens

cheatsheet-practicality-reviewer

Developer-practicality reviewer for OWASP cheat sheet changes. Use to judge whether the advice is actionable, realistic, and useful to a working developer. Invoked by /review-cheatsheet-pr.

OWASP/CheatSheetSeries · 49 tokens

cheatsheet-security-reviewer

Security-correctness reviewer for OWASP cheat sheet changes. Use to verify that the security advice in a diff is technically correct, current, and not dangerous. Invoked by /review-cheatsheet-pr.

OWASP/CheatSheetSeries · 49 tokens

threat-modeler

Use this agent when the user asks to "create a threat model", "analyze threats", "STRIDE analysis", "what are the threats", "threat modeling", "identify attack vectors", "map attack surface", or needs systematic threat identification with data flow diagrams.

allsmog/vuln-scout · 60 tokens