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.
/plugin marketplace add bdfinst/agentic-dev-team/plugin install security-assessmentWrote 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.
[](https://agentmods.dev/commands/bdfinst/agentic-dev-team/redteam-model)<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>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.
| Model | Per session | Once 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 |
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.
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)
- 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>. - Self-certification is logged. Artifact's SHA-256 is written to
harness/redteam/results/audit_log.jsonlwith the run timestamp. - Rate-limit + budget enforced. All HTTP goes through
http_clientwhich enforcesRATE_LIMITreq/sec andQUERY_BUDGETtotal queries. Exhaustion halts the pipeline withbudget_exhaustedstatus. - Harness-direct invocation blocked. The
redteam-guard.shhook refuses directpython orchestrator.pycalls unlessREDTEAM_AUTHORIZED=1is 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'sresult_store.resume_message()).
Flag interactions are in ${CLAUDE_PLUGIN_ROOT}/harness/redteam/ORCHESTRATION.md § "Flag
interactions".
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.
- 2d ago First seen · 77 lines · 36 tokens per session scan A 58f66ab247bd
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.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.