blackbox-vuln-orchestrator

Routes authorized black-box Web and API testing evidence into ranked next-action plans.

10|3|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill blackbox-vuln-orchestrator-baiqigo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blackbox-vuln-orchestrator
Source: https://github.com/baiqigo/baiqi-redteam-lab/tree/main/.agents/skills/blackbox-vuln-orchestrator
Command: npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill blackbox-vuln-orchestrator-baiqigo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Authorized black-box Web/API/CTF assessments often stall because scattered scanner hits, browser traffic, and fingerprints never become a coherent plan. This Skill turns recorded case evidence into an auditable, ranked queue of next validation steps and decides which specialist vulnerability Skill applies. ## Core Features & Use Cases - Evidence-driven routing: An offline router (next_action.py) scores candidate routes against observed signals, required capabilities, and prior attempts, suppressing disproven hypotheses instead of rescanning. - Scope and authorization gates: Every route requires declared authorization and locked scope; missing prerequisites produce WAIT or NEEDS_OPERATOR decisions rather than attack actions. - Specialist Skill dispatch: Maps signals to existing hunt-* Skills (IDOR, SSRF, XSS, SQLi, OAuth, file attacks, and more) with oracles, stop conditions, and chain-review rules that prevent treating RCE as a default goal. - Use Case: During an authorized web assessment, you record baseline observations in a case-state JSON, run the router, and receive the top three testable hypotheses with the exact specialist Skill, tool order, oracle, and stop conditions for each. ## Quick Start Ask the agent to run the blackbox-vuln-orchestrator on your authorized case-state JSON file and output the ranked next-action plan in Markdown.

Frequently Asked Questions about blackbox-vuln-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide the next step in a black-box web penetration test?

Record observations, capabilities, and prior attempts in a case-state JSON file, then run the offline next_action.py router. It scores candidate routes against routing rules and returns up to three ready hypotheses with the specialist Skill, tool order, oracle, and stop conditions for each.

What tools does this orchestrator coordinate for web testing?

It sequences Chrome browser inspection, Burp proxy traffic, Hunter MCP scanners, and optionally Kali tooling after a runtime precheck. The routing layer itself is offline and never sends requests or generates payloads.

Does the router work without declared authorization and scope?

No. Every routing rule requires authorization_declared and scope_locked capabilities. If either is missing, the router outputs NEEDS_SCOPE_OR_AUTHORIZATION and refuses to generate any testing action.

Why does the router suppress or refuse some vulnerability routes?

Routes are suppressed when prior attempts were marked DISPROVEN or EXHAUSTED, or when prerequisites like a second identity, controlled OAST, or isolated test window are missing. This prevents repeated scanning and unsafe high-impact actions.

Can this Skill be used on unauthorized or third-party targets?

No. It is explicitly designed only for user-authorized Web, API, CTF, and lab targets. Newly discovered hosts, third-party SaaS, and historical assets are treated as leads, not automatic scope expansion.