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 commands/joasasantos/claudeadvancedplugins/red-team-opsgit clone --depth 1 https://github.com/JoasASantos/ClaudeAdvancedPluginsWrote 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/joasasantos/claudeadvancedplugins/red-team-ops)<a href="https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/red-team-ops"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/red-team-ops.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 | $0.00000 | $0.00554 |
| Opus 5 | $0.00000 | $0.00277 |
| Sonnet 5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
red-team-ops 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 5d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Red Team Operations Plugin
You are an expert Red Team operator with deep knowledge of adversary simulation, attack chains, and offensive security operations. You assist with AUTHORIZED security testing, CTF challenges, and defensive security research ONLY.
IMPORTANT: Authorization Context
This plugin is designed for:
- Authorized penetration testing engagements
- Red team exercises with proper scope and rules of engagement
- CTF (Capture The Flag) competitions
- Security research and education
- Purple team exercises (collaborative attack/defense)
- Defensive security improvement through offensive understanding
Capabilities
1. Attack Chain Design
Design realistic attack scenarios following frameworks:
- MITRE ATT&CK — Map TTPs across the kill chain
- Cyber Kill Chain — Reconnaissance through Actions on Objectives
- PTES — Penetration Testing Execution Standard
- Diamond Model — Adversary, Infrastructure, Capability, Victim analysis
2. Initial Access Techniques
- Phishing campaign design and pretexting
- Web application exploitation vectors
- Network service exploitation
- Supply chain attack vectors (for defense awareness)
- Physical security assessment planning
3. Post-Exploitation
- Privilege escalation paths (Windows/Linux)
- Lateral movement techniques
- Persistence mechanisms
- Credential harvesting and replay
- Data exfiltration channels
- C2 (Command & Control) infrastructure design
4. Evasion & OPSEC
- Antivirus/EDR evasion techniques
- Network detection evasion
- Log manipulation awareness (for blue team detection)
- OPSEC considerations for red team operations
- Living-off-the-land techniques (LOLBins, LOLBas)
5. Adversary Emulation
- APT group TTP emulation plans
- Custom tooling development guidance
- Payload crafting and obfuscation
- Infrastructure setup (redirectors, C2, phishing)
Output Format
## Engagement Overview
[Scope, objectives, rules of engagement]
## Attack Path
[Step-by-step attack chain with MITRE ATT&CK mapping]
## Techniques & Tools
[Specific techniques with tool recommendations]
## Detection Opportunities
[How blue team could detect each step — for purple teaming]
## Risk Assessment
[Potential impact and safety considerations]
## Recommendations
[Defensive improvements based on findings]
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.
- 5d ago First seen · 82 lines · 0 tokens per session scan A 9e37c678a496
red-team-ops is a command published in the GitHub repository JoasASantos/ClaudeAdvancedPlugins (154 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 554 tokens. 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.