hypothesis-generator

Generate invariant-based vulnerability hypotheses from mapped web and API attack surface.

1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/mccleod1290/bb-agentic-setupv2 --skill hypothesis-generator-mccleod1290
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hypothesis-generator
Source: https://github.com/mccleod1290/bb-agentic-setupv2/tree/main/web-skills/hypothesis-generator
Command: npx skills add https://github.com/mccleod1290/bb-agentic-setupv2 --skill hypothesis-generator-mccleod1290

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Security testers often finish reconnaissance with a large endpoint inventory but no structured way to decide what to test first. This Skill converts Cartographer or threat-model outputs into ranked, falsifiable vulnerability hypotheses without executing any attacks, so testing stays evidence-driven and scoped. ## Core Features & Use Cases - Invariant-Based Hypothesis Generation: Maps endpoints, roles, tenants, and trust boundaries to security invariants (BOLA, BFLA, tenant isolation, CSRF, webhook verification, and more) and produces falsifiable hypotheses with control, mutation, and expected secure behavior. - Ranked Executor Queue: Outputs hypothesis_queue.json and hypothesis_queue.md prioritized by crown-jewel proximity, trust boundary, and evidence completeness, plus ready-to-copy executor and judge agent prompts. - Coverage Gap Tracking: Writes coverage_gaps.json and manual_validation_required.md listing exactly which accounts, tenants, or object pairs are missing before reliable testing can begin. - Use Case: After running recon on a multi-tenant SaaS target, feed notes/{target}/recon-data/endpoint_inventory.json into this Skill to produce a prioritized queue of cross-tenant, RBAC, and authorization hypotheses for a bounded executor agent. ## Quick Start Generate a hypothesis queue from the endpoint inventory at notes/my-target/recon-data/endpoint_inventory.json for target my-target.

Frequently Asked Questions about hypothesis-generator

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

FAQPage Schema
How do I generate vulnerability hypotheses from an endpoint inventory?▼

Run the generate_hypotheses.py script with your Cartographer endpoint_inventory.json, a target slug, and an output directory. It classifies endpoints by family, applies invariants, and writes hypothesis_queue.json plus markdown summaries.

What inputs does the hypothesis generator require?▼

It expects recon-data files such as endpoint_inventory.json, auth_contexts_roles.md, objects_and_identifiers.md, mechanisms_trust_boundaries.md, and threat-model outputs under notes/{target}/. Incomplete inputs still produce partial output with manual validation asks.

Does the hypothesis generator execute attacks or send requests?▼

No. It never sends traffic, runs payloads, or mutates live requests. It only produces hypotheses, mutation ideas, and evidence requirements; a separate bounded executor agent performs any actual testing.

What output files does the hypothesis generator create?▼

It writes hypothesis_queue.json, hypothesis_queue.md, invariant_matrix.md, endpoint_hypotheses.md, mechanism and RBAC hypothesis files, chain_candidates.md, manual_validation_required.md, coverage_gaps.json, and executor and judge agent prompts.

When should hypotheses be marked blocked_by_missing_cartography?▼

Use that status when recon data lacks the roles, tenants, object pairs, or control observations needed for a confident hypothesis. The Skill records the gap in coverage_gaps.json instead of inventing unsupported endpoints or assumptions.