Borrowing it
Nothing to install: this file belongs to terrene-foundation/metis. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/terrene-foundation/metis/main/.claude/commands/redteam.mdgit clone --depth 1 https://github.com/terrene-foundation/metisWrote 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/terrene-foundation/metis/redteam)<a href="https://agentmods.dev/commands/terrene-foundation/metis/redteam"><img src="https://agentmods.dev/badge/commands/terrene-foundation/metis/redteam.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.00019 | $0.01840 |
| Opus 5 | $0.00010 | $0.00920 |
| Sonnet 5 | $0.00004 | $0.00368 |
| Haiku 4.5 | $0.00002 | $0.00184 |
Grade A, and why
redteam 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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace Resolution
- If
$ARGUMENTSspecifies a project name, useworkspaces/$ARGUMENTS/ - Otherwise, use the most recently modified directory under
workspaces/(excludinginstructions/) - If no workspace exists, ask the user to create one first
- Read all files in
workspaces/<project>/briefs/for user context
Phase Check
- Verify
todos/active/is empty (all implemented) or note remaining items - Read
workspaces/<project>/03-user-flows/for validation criteria - Validation results go into
workspaces/<project>/04-validate/ - If gaps are found, document them and feed back to implementation (use
/implementto fix)
Execution Model
Autonomous execution model (see rules/autonomous-execution.md). Red team converges through iterative rounds. Findings are fixed autonomously, not reported for human triage.
Workflow
1. Spec compliance audit (MUST run first)
File existence is NOT compliance. Use the protocol in skills/spec-compliance/SKILL.md to verify each spec promise via AST parsing and targeted greps, NOT file existence or self-reports.
A "spec" is any documented promise about behavior, regardless of where it lives. Sources to audit:
specs/**— domain specifications (PRIMARY source of truth)workspaces/<project>/briefs/**— user-supplied requirementsworkspaces/<project>/01-analysis/**— analyst findings, deep analyses, design notesworkspaces/<project>/02-plans/**— implementation plans, ADRs, contractsworkspaces/<project>/todos/completed/**— what each todo claimed to deliver- Inline spec sections in README.md, CHANGELOG.md, or design docs the project references
For every spec promise found in these sources:
- Extract literal acceptance assertions from the spec text (class signatures, field names, decorator call sites, MOVE shim semantics, security tests, migration completion).
- Verify each assertion via grep or
ast.parseagainst the actual code. - Re-derive every check from scratch — do NOT trust
.spec-coverage,.test-results,convergence-verify.py, or any prior round's self-report. Self-reports are inputs to verify, not evidence to trust. - Save the assertion table to
workspaces/<project>/.spec-coverage-v2.md(the-v2suffix prevents confusion with legacy file-existence reports).
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.
- 6d ago First seen · 137 lines · 19 tokens per session scan A b2cd05c268cd
redteam is a command published in the GitHub repository terrene-foundation/metis (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,840 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.
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.