red-team-agent-orchestration: Command for Claude Code

.claude/commands/deck.md

deck is a command for Claude Code from Contoso-State/red-team-agent-orchestration. It costs 24 tokens per session (603 once invoked), scanned A, original, MIT.

A command that renders normalized security-assessment findings into Markdown slides suitable for conversion to PowerPoint. It expects findings, attack paths, engagement scope, and coverage-limit information from the assessment workflow.

In plain words
What is it for?
Use it after the reporting step to create an assessment deck with attack paths, concise bullets, and presenter notes.
Why use it?
It turns prepared assessment data into a consistent presentation format without manually filling a slide template.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is Contoso-State/red-team-agent-orchestration's own configuration. It tells Claude Code how to work on red-team-agent-orchestration itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything red-team-agent-orchestration configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Contoso-State/red-team-agent-orchestration. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Contoso-State/red-team-agent-orchestration/main/.claude/commands/deck.md
Clone the repo
git clone --depth 1 https://github.com/Contoso-State/red-team-agent-orchestration

Made for: Claude Code.

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 deck

README.md
[![agentmods](https://agentmods.dev/badge/commands/contoso-state/red-team-agent-orchestration/deck.svg)](https://agentmods.dev/commands/contoso-state/red-team-agent-orchestration/deck)
Your own site
<a href="https://agentmods.dev/commands/contoso-state/red-team-agent-orchestration/deck"><img src="https://agentmods.dev/badge/commands/contoso-state/red-team-agent-orchestration/deck.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 603 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00024 $0.00603
Opus 5 $0.00012 $0.00302
Sonnet 5 $0.00005 $0.00121
Haiku 4.5 $0.00002 $0.00060

Measured 7d ago against content hash dd25ca804578, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

deck 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 7d 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.

.claude/commands/deck.md · 49 lines

How it starts

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

/deck — Generate the Presentation Deck

You are acting as the Reporting Agent (agents/reporting/system-prompt.md). Produce a slide-ready Markdown deck that converts cleanly to PowerPoint.

Preconditions

  • engagements/<session>/reports/findings.json exists (run /report first). If it does not, run the /report normalization steps first, or tell the user to run /report.

Steps

  1. Load the normalized set from engagements/<session>/reports/findings.json and the attack paths, plus engagement.yaml for scope fields and engagements/<session>/inventory/coverage-limitations.json.

  2. Render engagements/<session>/reports/assessment-deck.md from reports/templates/assessment-deck.md, filling every {{placeholder}}. Keep the Marp frontmatter at the top intact.

  3. Respect the slide rules baked into the template so both converters work:

    • Every slide starts with a ## heading and slides are separated by ---.
    • One idea per slide; ≤ 6 bullets, ≤ 8 words each. Split long tables across slides.
    • Put any presenter detail in the trailing <!-- ... --> note, not on the slide.
  4. Feature attack paths — keep the "Top Attack Paths" slide plus one walked-through slide for the single most severe chain. Remove the extra per-path slide if there is only one path.

  5. Apply redaction from engagement.yaml data_handling (subscription/tenant IDs, UPNs, resource names) before writing. Never put secret values on a slide.

  6. Tell the user how to convert to .pptx:

    # Marp (recommended — honors the frontmatter theme)
    npx @marp-team/marp-cli engagements/<session>/reports/assessment-deck.md -o assessment-deck.pptx
    
    # Pandoc (alternative)
    pandoc engagements/<session>/reports/assessment-deck.md -o assessment-deck.pptx --slide-level=2
    

Read the full file on GitHub · 49 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. 7d ago First seen · 49 lines · 24 tokens per session scan A dd25ca804578

Subscribe to this mod's changes

deck is a command published in the GitHub repository Contoso-State/red-team-agent-orchestration (6 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 603 once invoked, about $0.0001 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.