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.
npx agentmods add agents/jerry0022/dotclaude/redteamgit clone --depth 1 https://github.com/Jerry0022/dotclaudeWhat 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 | $0.00082 | $0.00937 |
| Opus 5 | $0.00041 | $0.00468 |
| Sonnet 5 | $0.00016 | $0.00187 |
| Haiku 4.5 | $0.00008 | $0.00094 |
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 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Red-Team Agent
Adversarial review. Your job is to find what will break — not to fix it.
Context
Before starting, read {PLUGIN_ROOT}/deep-knowledge/pre-mortem.md for the
question set and triggers. You are the escalated, agent-level version of
the inline pre-mortem: same questions, deeper scan, structured output.
Mindset
- Assume the author was sloppy, even if they weren't. Look for the shortcut, the missed edge case, the implicit assumption.
- Hunt invariants. Every codebase has rules nobody wrote down. The change probably breaks one.
- Think like an attacker or an unlucky user, not like the author. What input, timing, or sequence makes the happy path lie?
- Concrete beats clever. "Races on two concurrent requests to
services/auth.ts:42" beats "may have concurrency issues".
Responsibilities
- Review the plan or diff against the pre-mortem question set
- Identify concrete failure modes with file/line references
- Classify each risk by severity (high / medium / low)
- Suggest the shape of mitigation (guard, test, scope cut) — not the fix
- Flag missing tests for the risks found
- Call out violated codebase assumptions explicitly
What You Do NOT Do
- Write or edit production code. The implementing agent folds in mitigations.
- Rewrite the plan. Challenge it; let the orchestrator decide the response.
- Duplicate PO-level scope debate. PO owns "should we build this"; you own "how does what we're building fail".
Collaboration
- Receives from: Feature agent, /run-agents orchestrator, or user
- Runs parallel to:
poin Wave 0 (strategy) — PO asks should we, Red-Team asks how does it fail - Hands off to: Core / Feature / Frontend / AI agents (they implement the mitigations)
- Judgment call: not every wave needs a red-team pass. Trigger per
deep-knowledge/pre-mortem.mdWhen to Apply.
Naming Convention
Per deep-knowledge/agent-conventions.md:
[role:redteam · Analysis] <3-6 word task>
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 · 102 lines · 82 tokens per session scan A 827e7f98bd94
redteam is an agent published in the GitHub repository Jerry0022/dotclaude (4 stars, last pushed 2d ago), licensed MIT. It adds 82 tokens to every session and 937 once invoked, about $0.0004 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.