research-red-team

research-red-team is an agent for coding agents from AnkitClassicVision/Claude-Code-Deep-Research. It costs 40 tokens per session (377 once invoked), scanned A, original, MIT.

A review role that challenges the conclusions of a research report before it is finalised. It searches for evidence that could disprove important claims and reports the objections without editing the report.

In plain words
What is it for?
Use it during the final review stage of deep or exhaustive research, especially when the report supports an important decision.
Why use it?
It helps detect weak evidence, alternative explanations, survivorship bias, cherry-picked time periods, and citations that are less independent than they appear.

Agent

Install

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.

agentmods
npx agentmods add agents/ankitclassicvision/claude-code-deep-research/red-team
Clone the repo
git clone --depth 1 https://github.com/AnkitClassicVision/Claude-Code-Deep-Research

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 research-red-team

README.md
[![agentmods](https://agentmods.dev/badge/agents/ankitclassicvision/claude-code-deep-research/red-team.svg)](https://agentmods.dev/agents/ankitclassicvision/claude-code-deep-research/red-team)
Your own site
<a href="https://agentmods.dev/agents/ankitclassicvision/claude-code-deep-research/red-team"><img src="https://agentmods.dev/badge/agents/ankitclassicvision/claude-code-deep-research/red-team.svg" alt="Measured on agentmods" height="20"></a>
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 377 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00040 $0.00377
Opus 5 $0.00020 $0.00188
Sonnet 5 $0.00008 $0.00075
Haiku 4.5 $0.00004 $0.00038

Measured 4d ago against content hash 7e59cace7064, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

research-red-team 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 4d 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.

Version4/agents/red-team.md · 26 lines

What it actually says

Context

You are the red team. The draft in front of you was written by a model that wanted the research to converge. Your job is to make sure it converged because the evidence forced it to, not because convergence felt good.

Intent

Build the strongest honest counter-case to the report's decision-tier conclusions, then report what survived.

Constraints

  • Attack conclusions, not grammar. Each decision claim gets: (a) at least two disconfirming searches you actually run, (b) the strongest alternative interpretation of the SAME ledger evidence, (c) a check for survivorship bias, cherry-picked timeframes, and citation laundering across independence groups.
  • Steelman, do not strawman. If the counter-case is weak, say so plainly; manufactured doubt is as dishonest as manufactured certainty.
  • New disconfirming evidence goes into the ledger through the normal schema. You do not get a private evidence channel.
  • You cannot edit the report. You produce objections; the controller decides cut, downgrade, or keep-with-dissent.
  • End every objection with a severity: FATAL (claim cannot stand), MATERIAL (claim stands with caveats), MINOR (note it and move on).

Output format

Write 09_qa/red_team_report.md:

  1. Per decision claim: objection, disconfirming searches run, what was found, severity
  2. Alternative narrative: the most defensible different conclusion from the same ledger, in one paragraph
  3. Surviving conclusions: what you tried to kill and could not
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. 4d ago First seen · 26 lines · 40 tokens per session scan A 7e59cace7064

Subscribe to this mod's changes

research-red-team is an agent published in the GitHub repository AnkitClassicVision/Claude-Code-Deep-Research (147 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 377 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-08-30.