agentmods.dev

bb-workflow

bb-workflow is a skill for Claude Code, Codex from Encod3d-Sec/TORCH. It costs 120 tokens per session (1,871 once invoked), scanned A, original, MIT.

An automated driver for running a bug-bounty campaign, where researchers look for and report security flaws in authorised targets.

In plain words
What is it for?
Use it to start or resume a campaign, run the required reconnaissance and testing phases, record tool choices, and mark findings, parked work, or dead ends.
Why use it?
It keeps the campaign state, required checks, evidence, and next action in one enforced workflow instead of relying on memory or improvised steps.

Skill for Claude CodeCodex

not rated 282 6d ago A scan 120 tokens original MIT
View the source file Encod3d-Sec/TORCH
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/encod3d-sec/torch/bb-workflow
Any agent
npx skills add Encod3d-Sec/TORCH --skill bb-workflow
Clone the repo
git clone --depth 1 https://github.com/Encod3d-Sec/TORCH

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 bb-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/encod3d-sec/torch/bb-workflow.svg)](https://agentmods.dev/skills/encod3d-sec/torch/bb-workflow)
Your own site
<a href="https://agentmods.dev/skills/encod3d-sec/torch/bb-workflow"><img src="https://agentmods.dev/badge/skills/encod3d-sec/torch/bb-workflow.svg" alt="Measured on agentmods" height="20"></a>
Per session 120 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,871 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 $0.00120 $0.01871
Opus 5 $0.00060 $0.00936
Sonnet 5 $0.00024 $0.00374
Haiku 4.5 $0.00012 $0.00187

Measured 4d ago against content hash c027c95d0ec6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bb-workflow 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 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.

Makes network callslowCapability

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

`curl` - a modern site's real attack surface is only visible rendered. Use the `chrome-devtools` MCP:
skills/workflow/bb-workflow/SKILL.md · 108 lines

How it starts

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

bb-workflow

The driver is the plan. You run one command, do exactly what it prints, record the result, repeat. Nothing here is advisory: the gates are enforced by scripts/campaign.py, so follow its output literally rather than improvising. This exists because prose routing failed - 22 Skill calls against 341 hand-rolled curls in the reference campaign; the board fixes that by making the mandate tool output, fresh every turn.

The loop

python3 scripts/campaign.py next        # prints ONE required-action block
# do EXACTLY what it lists, in order
python3 scripts/campaign.py note <row> --arsenal <slug>     # after Skill(wiki-arsenal)
python3 scripts/campaign.py done <row> --poc <img> --kind req   # | --dead R | --park Q | --find F
# repeat

Start / resume

  1. python3 scripts/campaign.py init --type bb - validates scope.md + the autonomy envelope, repairs engagement_type/schema, prints the Deadends size. If it exits 2, fix what it names (an empty scope.md is the one thing it cannot invent - fill it from the programme brief first).
  2. Passes 0-3 (OSINT/Wayback, crawl, fingerprint, CVE) feed state.md. Read every JS bundle and handler end to end (Skill-less; volume-reduce first: source-map, drop vendor, beautify, read). Grep never substitutes for the read.
  3. python3 scripts/campaign.py board - writes the killchain 4a rows. Refuses on an empty state.
  4. Enter the loop. next serves one row, depth-first, one open row at a time.

Browser observation (chrome-devtools MCP)

The programme's targets are internet-reachable, so drive them through a real browser, not just curl - a modern site's real attack surface is only visible rendered. Use the chrome-devtools MCP:

  • Pass 1 crawl: navigate_page to each app, then list_network_requests - the XHR/fetch calls a page makes reveal the API endpoints/routes a static crawl never sees (this is exactly the lead a curl-only recon misses). take_snapshot for the rendered DOM; evaluate_script to read client config / __NEXT_DATA__ / JS globals.
  • Confirmation + evidence: DOM-XSS fires in the real DOM (evaluate_script / console); a rendered take_screenshot of the exploited state is a valid web PoC (G3).

Read the full file on GitHub · 108 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. 4d ago First seen · 108 lines · 120 tokens per session scan A c027c95d0ec6

Subscribe to this mod's changes

bb-workflow is a skill published in the GitHub repository Encod3d-Sec/TORCH (282 stars, last pushed 6d ago), licensed MIT. It adds 120 tokens to every session and 1,871 once invoked, about $0.0006 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.

Security
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

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

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