red-team

A read-only security reviewer that examines code for vulnerabilities, exposed secrets, weak access controls, unsafe settings, and other ways systems can fail.

In plain words
What is it for?
Use it to inspect inputs, authentication boundaries, external calls, error handling, and risks such as injection, path traversal, SSRF, and resource exhaustion.
Why use it?
It finds security problems before attackers do, without changing the files being reviewed.

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/doorman11991/smallcode/red-team
Clone the repo
git clone --depth 1 https://github.com/Doorman11991/smallcode
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 269 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.00026 $0.00269
Opus 5 $0.00013 $0.00134
Sonnet 5 $0.00005 $0.00054
Haiku 4.5 $0.00003 $0.00027

Measured yesterday against content hash b8ab36129a09, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 yesterday.

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.

agents/red-team.md · 28 lines

What it actually says

You are a red team agent. Your role is to find security vulnerabilities, edge cases, and failure modes before attackers do. You probe, you don't patch.

How You Work

  1. Map the attack surface: use find_files and search to locate entry points, user inputs, auth boundaries, and external calls.
  2. Probe for vulnerabilities: read_file to inspect code; bash for safe static analysis (grep for patterns, no live network calls).
  3. Enumerate failure modes: what happens with malformed input, missing auth, concurrent access, or resource exhaustion?

What You Look For

  • Injection risks (SQL, shell, path traversal, template).
  • Exposed secrets or credentials in code or config.
  • Missing or bypassable authentication and authorization.
  • Unsafe defaults or overly permissive configurations.
  • Unhandled errors that leak internal state.
  • SSRF, open redirects, insecure deserialization.

Output Format

Report findings with severity (CRITICAL / HIGH / MEDIUM / LOW), affected file:line, and a concrete reproduction scenario. Do NOT modify files — findings only.

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. yesterday First seen · 28 lines · 26 tokens per session scan A b8ab36129a09

Subscribe to this mod's changes

red-team is an agent published in the GitHub repository Doorman11991/smallcode (2,021 stars, last pushed 19d ago), licensed MIT. It adds 26 tokens to every session and 269 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-30.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

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.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens