GITEST

Architecture

GITEST uses a modular playbook-driven architecture with runtime intelligence integration and an optional GiDom bridge for pre-recon.

Directory Structure

code
GITEST/
├── GiScan/
│   ├── intelligence/        # 18 JSON runtime data layers
│   ├── playbooks/           # 250+ skill playbooks
│   └── scripts/
│       └── tools-catalog.json  # 109 tools catalog
├── .opencode/
│   └── commands/
│       ├── gitest.md        # Full exploitation pipeline
│       └── gidom.md         # Domain recon + auth engine
├── ~/.gidom/
│   ├── wordlists/           # 3 auto-downloaded wordlist sources
│   └── bridge/              # GiDom → GITEST bridge JSON files
├── SCAN/
│   └── targets/[domain]/    # Per-target output directory
├── .github/
│   └── assets/              # Logos & branding
├── AGENTS.md                # Agent configuration
├── setup.sh                 # Installs both gitest.md + gidom.md
└── README.md

Core Components

Playbook Engine

The core of GITEST. Each playbook is a directory containing a single SKILL.md — a structured markdown file with:

  • Metadata: name, description, trigger keywords
  • Execution Phases: Step-by-step detection (Phase 1, 2, ...)
  • Tool Commands: Ready-to-run commands with template variables

Intelligence Layers

18 JSON files in GiScan/intelligence/ provide runtime context, including:

  • Vuln ontology, attack chains, CVE correlations
  • WAF signatures and bypass profiles
  • Port/tech correlations, endpoint patterns
  • Skill keywords and verification patterns

GiDom Bridge

GiDom is a companion command for fast domain recon + auth. It writes a bridge JSON file that GITEST auto-detects:

  1. Run /gidom https://target.com — 13 phases: recon, login surface, auth, dual-mode scan
  2. Run /gitest https://target.com — auto-imports bridge data, skips redundant recon
  3. Benefit: saves 15-30 min per target, seeds exploitation with pre-discovered targets

GiDom features a built-in auth engine that handles HTML form login, JSON API authentication, and basic auth — with CSRF token extraction, rules/terms acceptance, and post-auth deep scanning.

Pipeline Orchestrator

The pipeline runs through 11 sequential phases with GiDom feeding pre-recon data:

code
GiDom:  SETUP → RECON → AUTH → DUAL SCAN → BRIDGE
GITEST: RECON → OSINT → CODE ANALYSIS → CMS/CRM → API → AUTH →
        SUPPLY CHAIN → CLOUD → EXPLOITATION → POST-EXPLOITATION → REPORTING

Each phase dynamically selects playbooks based on discovered technologies and open ports.

Tools Catalog

109 tools in GiScan/scripts/tools-catalog.json with structured format including installation commands and platform detection.

Previous← RequirementsNextPipeline Phases →