caido-mode

Controls Caido via SDK CLI to search, edit, replay, and fuzz HTTP traffic.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @caido/sdk-client, graphql-tag, tsx.

What problem does it solve? Manually copy-pasting large session cookies, JWTs, and CSRF tokens into every test request is slow and error-prone. This Skill lets you find an authenticated request in Caido's HTTP history and modify only the path, method, or body while preserving all auth context, so security testing happens entirely through the Caido proxy with full visibility. ## Core Features & Use Cases - HTTP History Search & Edit-Replay: Query traffic with HTTPQL, then edit and resend requests with auth headers intact for IDOR, privilege escalation, and header bypass testing. - Full Caido Management: Manage scopes, filter presets, environments, replay sessions/collections, projects, hosted files, tasks, and intercept state from the terminal. - Findings & PoC Export: Create deduplicated findings linked to requests and export any request as a ready-to-use curl command for reports. - Use Case: During an authorized bug-bounty test, search for req.path.cont:"/api/user", edit the request ID to change the user ID parameter, confirm the IDOR, then create a finding and export a curl PoC — all without leaving the CLI. ## Quick Start Ask the AI to run the caido-client health command to verify the connection, then search recent requests and edit one to test a different API path.

Frequently Asked Questions about caido-mode

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

FAQPage Schema
How do I replay and edit HTTP requests with Caido from the command line?▼

Use the edit command with a request ID from Caido's history, passing flags like --path, --method, --body, or --set-header. It preserves all cookies and auth headers from the original request while changing only what you specify, then sends it through Caido.

How do I search Caido HTTP history with HTTPQL?▼

Run the search command with an HTTPQL query such as 'req.method.eq:"POST" AND resp.code.eq:200'. String values must be quoted, integers unquoted, and there is no NOT operator — use negated variants like ncont, ne, or nregex instead.

What authentication does the Caido SDK client require?▼

It requires a Personal Access Token created in Caido under Dashboard → Developer → Personal Access Tokens. Run the setup command once with the PAT, or set the CAIDO_PAT environment variable; tokens are cached in ~/.claude/config/secrets.json.

Can I fuzz endpoints with Caido from the CLI?▼

Yes, create an automate session from a request ID with create-automate-session, configure payload markers and wordlists in the Caido UI, then start it with the fuzz command. Payload configuration itself is not yet exposed through the SDK.

Why does the Caido client fail to connect or report auth errors?▼

Connection failures usually mean Caido is not running at the configured URL (default http://localhost:8080) — check with the health command. Auth errors mean the PAT is missing or invalid; run auth-status to diagnose and re-run setup with a valid token.