red-team-tactics

red-team-tactics is a skill for Claude Code, Codex from bugrabilge/bilge-development-kit. It costs 25 tokens per session (2,006 once invoked), scanned B, original, MIT.

A guide to authorized penetration testing, which checks systems by simulating attacks to find security weaknesses before criminals do.

In plain words
What is it for?
Use it to scope security tests, map an application's attack surface, test against OWASP guidance, document findings, and recommend remediation.
Why use it?
It provides a structured way to discover vulnerabilities, limit testing safely, assess impact, and report fixes with evidence.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to scope security tests, map an application's attack surface, test against OWASP guidance, document findings, and recommend remediation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bugrabilge/bilge-development-kit/red-team-tactics
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.

Any agent
npx skills add bugrabilge/bilge-development-kit --skill red-team-tactics
Clone the repo
git clone --depth 1 https://github.com/bugrabilge/bilge-development-kit

Made for: Claude Code, Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/red-team-tactics/github.svg)](https://agentmods.dev/skills/bugrabilge/bilge-development-kit/red-team-tactics)
Your own site
<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/red-team-tactics"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/red-team-tactics/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.

agentmods 80×15 button for red-team-tactics

Your own site · 80×15
<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/red-team-tactics"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/red-team-tactics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,006 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00025 $0.02006
Opus 5 $0.00013 $0.01003
Sonnet 5 $0.00005 $0.00401
Haiku 4.5 $0.00003 $0.00201

Measured 5d ago against content hash 8697f4bfb770, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade B, and why

red-team-tactics scanned grade B with 1 finding 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.

Cloud metadata endpointmediumServer-side request forgery

One request to 169.254.169.254 can return temporary IAM credentials.

- Try internal addresses: `127.0.0.1`, `169.254.169.254` (cloud metadata), `localhost`

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

skills/red-team-tactics/SKILL.md · 197 lines

How it starts

The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Red Team Tactics

"To know your enemy, you must become your enemy." -- Sun Tzu

When to Use

  • Planning and executing penetration tests against web applications
  • Following OWASP Testing Guide methodology
  • Identifying and exploiting security weaknesses in applications
  • Performing reconnaissance and attack surface mapping
  • Writing professional penetration test reports
  • Understanding attacker mindset to improve defensive security
  • Simulating real-world attack scenarios

Penetration Testing Methodology

Phases of Engagement

  1. Scoping: Define targets, rules of engagement, and boundaries
  2. Reconnaissance: Gather intelligence about the target
  3. Enumeration: Map the attack surface in detail
  4. Vulnerability Analysis: Identify potential weaknesses
  5. Exploitation: Attempt to exploit discovered vulnerabilities
  6. Post-Exploitation: Assess the impact of successful exploitation
  7. Reporting: Document findings with evidence and remediation guidance

Rules of Engagement

  • Always have written authorization before testing
  • Define in-scope and out-of-scope systems explicitly
  • Agree on testing windows and communication procedures
  • Establish emergency contacts and stop conditions
  • Document any production impact risks and obtain acknowledgment
  • Never access, modify, or exfiltrate real user data

Reconnaissance

Passive Reconnaissance (OSINT)

No direct interaction with the target:

  • Domain enumeration: WHOIS, DNS records, certificate transparency logs
  • Subdomain discovery: crt.sh, SecurityTrails, Amass passive mode
  • Technology fingerprinting: Wappalyzer, BuiltWith, HTTP headers
  • Code exposure: GitHub/GitLab search for organization repos, leaked credentials
  • Employee enumeration: LinkedIn, job postings reveal tech stack
  • Archived pages: Wayback Machine for old endpoints and configurations
  • Google dorking: site:target.com filetype:pdf, inurl:admin, intitle:"index of"

Active Reconnaissance

Direct interaction with target systems:

  • Port scanning: Nmap for service discovery and version detection
  • Web spidering: Crawl the application to map all pages and forms
  • Directory brute-forcing: ffuf, feroxbuster, gobuster for hidden paths
  • API discovery: Check /swagger, /api-docs, /graphql, /.well-known/
  • Technology profiling: HTTP response headers, error messages, cookies

Read the full file on GitHub · 197 lines

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. 5d ago First seen · 197 lines · 25 tokens per session scan B 8697f4bfb770

Subscribe to this mod's changes

red-team-tactics is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 2,006 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (cloud metadata endpoint). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

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

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens