chain-construct

chain-construct is a skill for Claude Code, Codex from mtarcure/claude-vibe-squad. It costs 0 tokens per session (817 once invoked), scanned A, original, MIT.

A method for combining several weak bug-bounty observations into one demonstrated attack chain. The goal is to show a complete security impact, such as account takeover, unauthorized access, data exposure, or stolen funds.

In plain words
What is it for?
Use it to define the impact, identify the attacker's starting point, connect possible weaknesses, and verify the final result.
Why use it?
Individual clues may not prove a serious vulnerability; linking them can show whether an attacker can reach a concrete harmful end state.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to define the impact, identify the attacker's starting point, connect possible weaknesses, and verify the final result.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mtarcure/claude-vibe-squad/chain-construct
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 mtarcure/claude-vibe-squad --skill chain-construct
Clone the repo
git clone --depth 1 https://github.com/mtarcure/claude-vibe-squad

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 chain-construct

README.md
[![agentmods](https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/chain-construct/github.svg)](https://agentmods.dev/skills/mtarcure/claude-vibe-squad/chain-construct)
Your own site
<a href="https://agentmods.dev/skills/mtarcure/claude-vibe-squad/chain-construct"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/chain-construct/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 chain-construct

Your own site · 80×15
<a href="https://agentmods.dev/skills/mtarcure/claude-vibe-squad/chain-construct"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/chain-construct.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 817 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00000 $0.00817
Opus 5.5 $0.00000 $0.00327
Sonnet 5.5 $0.00000 $0.00163
Haiku 4.5 $0.00000 $0.00082

Measured 1mo ago against content hash 38e22f1d9081, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

chain-construct 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 1mo 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.

.agents/skills/chain-construct/SKILL.md · 57 lines

How it starts

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

chain-construct

Generic multi-step attack-chain builder. Turn a set of individually-weak observations into a single demonstrated exploit chain whose end state proves realized impact. Domain skills specialize this — e.g. chain-construct-smart-contract adds EVM/Solana primitives. Use when a finding requires more than one step to reach impact, or when several low-severity leads may compose into a payout-class result (RCE, auth-bypass, privilege-escalation/ATO, private-data, funds theft).

Method

  1. Fix the objective as an end state, not a step. Write the impact you must demonstrate as a checkable predicate ("attacker balance increased by X without deposit", "attacker holds admin role", "victim record disclosed"). A chain is valid only when the final state satisfies that predicate — reachability of an intermediate step is not the objective.
  2. Map the chain head. Identify the first thing the attacker actually controls (an input, an externally-callable entry point, a crafted account/message). Everything upstream of it is a precondition, not part of the chain.
  3. List candidate links. For each confirmed or suspected weakness, record: what it lets the attacker do, what state it changes, and what precondition it needs. A link is only usable if its precondition is satisfiable by the attacker or by an earlier link's output.
  4. Order links by state-feeds. Link A precedes B iff A's output state satisfies B's precondition. Reject any ordering that requires a precondition no earlier link (or the attacker) can produce.
  5. Build the minimal chain. Prefer the shortest ordering that reaches the objective. Drop links that do not move state toward the predicate.
  6. Prove it, don't assert it. Author a runnable reproduction (test/harness/script) that executes the chain end-to-end and asserts the objective predicate on the final state. A theoretical chain is a lead, not a finding, until the reproduction passes.
  7. Document preconditions honestly. State every environmental precondition the chain needs (specific state, funds available, a block/time delta, a fork block number). A chain that only works under an unstated precondition is not portable and must say so.

Read the full file on GitHub · 57 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. 1mo ago First seen · 57 lines · 0 tokens per session scan A 38e22f1d9081

Subscribe to this mod's changes

chain-construct is a skill published in the GitHub repository mtarcure/claude-vibe-squad (165 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 817 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-09-19.