exploit-chain-building

exploit-chain-building is a skill for Claude Code, Codex from woohyun212/security-skill. It costs 30 tokens per session (2,407 once invoked), scanned A, original, MIT.

A security-testing guide for combining confirmed low- or medium-severity findings into a multi-step attack path.

In plain words
What is it for?
Use it during penetration tests, bug-bounty investigations, and report preparation to test exploit chains and assess their combined severity.
Why use it?
It helps show when separate weaknesses can produce greater impact together than they do individually.

Skill for Claude CodeCodex

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

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 skills/woohyun212/security-skill/exploit-chain-building
Any agent
npx skills add woohyun212/security-skill --skill exploit-chain-building
Clone the repo
git clone --depth 1 https://github.com/woohyun212/security-skill

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 exploit-chain-building

README.md
[![agentmods](https://agentmods.dev/badge/skills/woohyun212/security-skill/exploit-chain-building.svg)](https://agentmods.dev/skills/woohyun212/security-skill/exploit-chain-building)
Your own site
<a href="https://agentmods.dev/skills/woohyun212/security-skill/exploit-chain-building"><img src="https://agentmods.dev/badge/skills/woohyun212/security-skill/exploit-chain-building.svg" alt="Measured on agentmods" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,407 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.1 $0.00030 $0.02407
Opus 5 $0.00015 $0.01203
Sonnet 5 $0.00006 $0.00481
Haiku 4.5 $0.00003 $0.00241

Measured 6d ago against content hash 95aadff53deb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

exploit-chain-building scanned grade A 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 6d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- `curl` installed for HTTP-based chain verification
exploit-chain-building/SKILL.md · 216 lines

How it starts

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

What this skill does

Guides a security researcher from a confirmed low or medium severity finding through a structured escalation process to discover multi-step exploit chains that demonstrate significantly higher impact. Uses a chain table of known A→B→C escalation paths, tests each link in the chain for exploitability, and produces a combined CVSS score and step-by-step proof-of-concept that reflects the full chain impact rather than individual finding severity.

When to use

  • When a confirmed finding is rated Low or Medium but feels like it could enable more
  • When a bug bounty report needs to demonstrate maximum impact to justify a higher payout
  • During a penetration test to escalate a foothold into a more significant compromise
  • When triage shows multiple low-severity findings that may combine into a critical chain
  • Before finalizing a report — to check whether any finding enables a higher-impact chain

Prerequisites

  • At least one confirmed, reproducible finding as a starting point
  • curl installed for HTTP-based chain verification
  • Burp Suite or equivalent HTTP proxy (recommended for interactive chain testing)
  • Access to the target application with a test account
  • Written authorization for all testing activities

Inputs

Variable Required Description
SECSKILL_INITIAL_FINDING required Description of the confirmed starting vulnerability (e.g. Self-XSS in profile bio field)
SECSKILL_TARGET_URL required Base URL of the target application
SECSKILL_AUTH_TOKEN optional Session cookie or Bearer token for the test account
SECSKILL_OUTPUT_DIR optional Directory to save chain evidence (default: ./output)

Workflow

Step 1: Confirm the initial finding

Before attempting escalation, verify the starting vulnerability is reliably reproducible. Document the exact steps, request, and response.

export TARGET="${SECSKILL_TARGET_URL:?Set SECSKILL_TARGET_URL}"
export FINDING="${SECSKILL_INITIAL_FINDING:?Set SECSKILL_INITIAL_FINDING}"
export OUTDIR="${SECSKILL_OUTPUT_DIR:-./output}"
export AUTH="${SECSKILL_AUTH_TOKEN:-}"
mkdir -p "$OUTDIR"

echo "[*] Starting finding: $FINDING"
echo "[*] Target: $TARGET"
echo "[*] Reproduce the finding and save evidence to: $OUTDIR/step1_initial_finding.txt"

Read the full file on GitHub · 216 lines

Files

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.

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. 6d ago First seen · 216 lines · 30 tokens per session scan A 95aadff53deb

Subscribe to this mod's changes

exploit-chain-building is a skill published in the GitHub repository woohyun212/security-skill (21 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 2,407 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

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

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 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