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 skills add pr-purgatory/redteam-skill --skill redteamgit clone --depth 1 https://github.com/pr-purgatory/redteam-skillWrote 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/skills/pr-purgatory/redteam-skill/redteam)<a href="https://agentmods.dev/skills/pr-purgatory/redteam-skill/redteam"><img src="https://agentmods.dev/badge/skills/pr-purgatory/redteam-skill/redteam/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/pr-purgatory/redteam-skill/redteam"><img src="https://agentmods.dev/badge/skills/pr-purgatory/redteam-skill/redteam.svg" alt="Reviewed on agentmods" width="80" 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.00041 | $0.00405 |
| Opus 5.5 | $0.00016 | $0.00162 |
| Sonnet 5.5 | $0.00008 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00040 |
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 2mo 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.
What it actually says
Redteam Skill
Overview
This skill implements a comprehensive red teaming methodology to identify weaknesses, blind spots, and potential improvements in a codebase. It investigative failures from multiple angles including security, architecture, and logic.
Workflow
- Analyze: Audit the codebase using the specialized lenses defined in criteria.md.
- Report: Save all findings to
RedTeamFindings.mdin the workspace root. - Default Output Format:
* [Module/File] [Vulnerability Name or CVE] - [One-line description]
- Verbose Output Format:
- Triggered by "verbose", "detailed", or "/redteam --verbose".
- Include sub-bullets for each finding:
- Finding: [Detailed explanation of the technical root cause]- Exploit: [Step-by-step description of how an attacker would leverage this]- Resolution: [Actionable code changes or configuration fixes to mitigate]
Usage Examples
/redteam: Run standard audit./redteam verbose: Run audit with detailed exploit and resolution notes.- "red team the auth module": Perform a targeted audit on a specific component.
Methodology
The skill uses 10+ investigative angles including:
- Premortem Analysis: Why would this fail in 6 months?
- Security Audit: Auth bypass and privilege escalation.
- Architecture Stress: 100x load failure points.
- Supply Chain: Dependency vulnerabilities.
- Abuse Scenarios: Weaponization for spam/DDoS.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 35 lines · 41 tokens per session scan A f736a2a9e45f
redteam is a skill published in the GitHub repository pr-purgatory/redteam-skill (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 405 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…