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 skills/jessefmoore/offensive-claude-code/advanced-redteamnpx skills add jessefmoore/offensive-claude-code --skill advanced-redteamgit clone --depth 1 https://github.com/jessefmoore/offensive-claude-codeWrote 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/jessefmoore/offensive-claude-code/advanced-redteam)<a href="https://agentmods.dev/skills/jessefmoore/offensive-claude-code/advanced-redteam"><img src="https://agentmods.dev/badge/skills/jessefmoore/offensive-claude-code/advanced-redteam.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.02745 |
| Opus 5 | $0.00000 | $0.01373 |
| Sonnet 5 | $0.00000 | $0.00549 |
| Haiku 4.5 | $0.00000 | $0.00275 |
Grade A, and why
advanced-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 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.
How it starts
The opening of the file, as written. The whole thing — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: advanced-redteam-ops description: Advanced red team operations — OPSEC discipline, C2 infrastructure design, redirectors, malleable profiles, living-off-the-land, data exfiltration, infrastructure segregation metadata: type: offensive phase: operations
Advanced Red Team Operations
When to Activate
- Planning advanced red team engagements
- Designing C2 infrastructure with OPSEC
- Understanding APT TTPs and operational security
- Long-term persistent access scenarios
C2 Infrastructure Design
Redirectors (Never Expose Team Server Directly)
Rule: Team server ONLY binds to localhost. NEVER bind to 0.0.0.0 or external interface.
# Cobalt Strike team server (bind locally)
./TeamServerImage -Dcobaltstrike.server_port=50050 \
-Dcobaltstrike.server_bindto=127.0.0.1 \
-Djavax.net.ssl.keyStore=./cobaltstrike.store \
teamserver 127.0.0.1 <password>
# Tunnel via websocat (CStrike uses raw TCP, smuggle in WebSocket)
websocat -E -b ws-l:127.0.0.1:40000 tcp:127.0.0.1:50050 &
# Cloudflare tunnel (or ngrok)
cloudflared tunnel --url http://127.0.0.1:40000 --no-autoupdate
# Or: named tunnel via Zero Trust → point to domain + UUID path
# On operator machine:
websocat -E -b tcp-l:127.0.0.1:2222 ws://mytunnel.domain.com/<uuid> &
# Connect CStrike client to 127.0.0.1:2222
Benefits:
- Team server never exposed to internet scanning (Shodan, Censys)
- Cloudflare/CDN provides high-reputation front
- Easy to rotate infrastructure — just change tunnel endpoint
Smart Redirectors (Filter Blue Team)
# Nginx redirector with filtering
server {
listen 443 ssl;
server_name legit-looking.com;
ssl_certificate /path/to/cert.pem;
ssl_certificate_key /path/to/key.pem;
# Only forward traffic matching Malleable C2 profile
location /api/v2/session {
# Check custom header (beacon identifier)
if ($http_x_session_id != "valid-beacon-id") {
return 301 https://microsoft.com$request_uri;
}
# Check User-Agent matches profile
if ($http_user_agent !~* "Mozilla/5.0.*Teams") {
return 301 https://microsoft.com$request_uri;
}
# Forward to team server
proxy_pass https://127.0.0.1:8443;
proxy_ssl_verify off;
}
# Deflect all other traffic to legitimate site
location / {
return 301 https://microsoft.com$request_uri;
}
}
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.
- 4d ago First seen · 312 lines · 0 tokens per session scan A 1c2a078d8cc6
advanced-redteam is a skill published in the GitHub repository jessefmoore/offensive-claude-code (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,745 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…