redteam-model

redteam-model is a command for Claude Code from bdfinst/agentic-dev-team. It costs 36 tokens per session (844 once invoked), scanned A, original, MIT.

A safety-controlled test harness for attacking a model endpoint that you own. It runs seven adversarial checks, limits request rate and total queries, and records the run and its results for review.

In plain words
What is it for?
Use it to red-team a self-owned model service, inspect probe results, and create an audit trail of the test run.
Why use it?
It helps reveal how a machine-learning model behaves under hostile or unusual inputs while restricting tests to approved targets. The audit log provides a record of what was tested.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the security-assessment plugin — 3 skills, 5 commands, 13 agents shipped together

Good fit Use it to red-team a self-owned model service, inspect probe results, and create an audit trail of the test run.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add bdfinst/agentic-dev-team
Claude Code
/plugin install security-assessment

Made for: Claude Code.

Or install security-assessment, the plugin that ships this one along with the rest of its 3 skills, 5 commands, 13 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 redteam-model

README.md
[![agentmods](https://agentmods.dev/badge/commands/bdfinst/agentic-dev-team/redteam-model.svg)](https://agentmods.dev/commands/bdfinst/agentic-dev-team/redteam-model)
Your own site
<a href="https://agentmods.dev/commands/bdfinst/agentic-dev-team/redteam-model"><img src="https://agentmods.dev/badge/commands/bdfinst/agentic-dev-team/redteam-model.svg" alt="Measured on agentmods" height="20"></a>
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 844 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.00036 $0.00844
Opus 5 $0.00018 $0.00422
Sonnet 5 $0.00007 $0.00169
Haiku 4.5 $0.00004 $0.00084

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

Security

Grade A, and why

redteam-model 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 2d 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.

plugins/security-assessment/commands/redteam-model.md · 77 lines

How it starts

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

/redteam-model

Orchestrator entry point for the adversarial ML red-team harness. Perform scope + consent checks, then dispatch the Python orchestrator at ${CLAUDE_PLUGIN_ROOT}/harness/redteam/orchestrator.py. Interpret probe artifacts via the four analyzer agents after the Python passes complete.

Full runtime spec — including bash invocations, exact refusal wording, flag-interaction matrix, and step output formats — is in ${CLAUDE_PLUGIN_ROOT}/harness/redteam/ORCHESTRATION.md. Read it before dispatching.

Safety constraints (non-negotiable)

  1. Scope-enforced by default. Targets must resolve to a self-owned CIDR (127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, ::1). Public targets require --self-certify-owned <path>.
  2. Self-certification is logged. Artifact's SHA-256 is written to harness/redteam/results/audit_log.jsonl with the run timestamp.
  3. Rate-limit + budget enforced. All HTTP goes through http_client which enforces RATE_LIMIT req/sec and QUERY_BUDGET total queries. Exhaustion halts the pipeline with budget_exhausted status.
  4. Harness-direct invocation blocked. The redteam-guard.sh hook refuses direct python orchestrator.py calls unless REDTEAM_AUTHORIZED=1 is in env. This command sets it after the scope/consent checks pass; scoped to the child process only.

Parse arguments

Arguments: $ARGUMENTS

Positional: <target-url> (base URL, no trailing slash).

Flags:

  • --self-certify-owned <path>: authorization artifact for public targets. Format: knowledge/redteam-authorization.md.
  • --dry-run: validate config + scope + consent; print step graph; zero HTTP requests. Scope enforcement still runs.
  • --agents <id> [<id> ...]: run only these probe IDs (01-08).
  • --start <id>: resume from this probe ID (token from prior run's result_store.resume_message()).

Flag interactions are in ${CLAUDE_PLUGIN_ROOT}/harness/redteam/ORCHESTRATION.md § "Flag interactions".

Read the full file on GitHub · 77 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. 2d ago First seen · 77 lines · 36 tokens per session scan A 58f66ab247bd

Subscribe to this mod's changes

redteam-model is a command published in the GitHub repository bdfinst/agentic-dev-team (280 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 844 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-09-05.