Playbooks / A practical companion

Stay in the loop.

Learn the craft, one request at a time.

Twelve hands-on chapters. Set your scope, follow the traffic, test an idea, and turn what you find into evidence.

Start reading Explore the chapters
Playbooks The gori
field guide. From capture to report

Four parts / 12 chapters

Contents

Read from the beginning or open the chapter you need. Every workflow has checkpoints to help you see what worked.

Start β†’

Foundations

  1. Set up an engagementCreate a project, draw a scope, and lock the test inside a sandbox: the guardrails every active tool checks before it fires.
  2. Map the attack surfaceFold a scoped capture into a host→path tree, then let Discover surface the endpoints you never clicked.

The manual loop

  1. Intercept and modify in flightHold a request mid-flight, change it, let it continue, then make the change stick as a rule.
  2. Fuzz a parameterMark one part of a captured request, throw a wordlist at it, and read the responses that stand out.
  3. Carry a sessionLog in once, capture the token, and replay every later request as an authenticated user, by hand and headless.

Workbenches

  1. Decode and transform dataChain converters into a pipeline (decode, decode again, hash) and watch each step's output, then save it for reuse.
  2. Attack a JWTDecode a JSON Web Token, tamper with its claims, and test whether the server actually verifies the signature.
  3. Crack and forge session cookiesRead a signed Flask, Rack, or Django cookie, recover the secret that signs it, and mint your own.
  4. Grade token randomnessCollect a few hundred session tokens and let the Sequencer score how predictable they are.
  5. Confirm blind vulnerabilities with OASTSome bugs never show in the response. Prove them by making the server call you, and catch the callback.

Wrap up

  1. Triage and reportTurn scattered findings into issues, prove a fix with a diff, and export a report a teammate can read.
  2. Run an AI co-pilot sessionPut an agent on the same project over MCP and keep its consequential actions visible. The intelligence lives outside the tool, by design.

Before you begin

Playbooks send real traffic. Point gori only at a target you are authorized to test, and keep it in scope. If you have not yet captured and replayed a request, take the ten-minute Quick Start first.

How to use this field guide

Start with Foundations, then follow the chapters in order or open the part that matches your task. Every procedure ends with a Checkpoint: the exact state you should see before moving on. If a checkpoint fails, stop there and use the linked guide to understand the tool before continuing.

Keep a reference nearby

Use the Guide for in-depth explanations of each workbench and the Reference for exact CLI commands, configuration keys, and query-language syntax.