caido-mode

Edit authenticated Caido HTTP requests without losing cookies or tokens.

260|26|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/caido/skills --skill caido-mode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caido-mode
Source: https://github.com/caido/skills/tree/main/skills/caido-mode
Command: npx skills add https://github.com/caido/skills --skill caido-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious manual work of copy-pasting large session cookies and authentication tokens when testing authenticated web endpoints, removing the risk of human error and streamlining security testing workflows that require preserved authentication context.

Core Features & Use Cases

  • Preserved Auth Request Editing: Modify paths, methods, headers, or request bodies of existing authenticated requests without losing cookies or tokens, ideal for IDOR, privilege escalation, and header bypass testing.
  • Comprehensive Caido API Access: Interact with all Caido features including HTTP history search via HTTPQL, replay session and collection management, scope/filter/environment configuration, findings creation, and intercept control directly from the terminal.
  • Real-World Use Case: A security tester can locate an authenticated request in Caido's history, edit the user ID parameter to test for insecure direct object references, and export the modified request as a curl command for reporting, all without manually handling authentication headers.

Quick Start

Use the caido-mode skill to search Caido's HTTP history for an authenticated POST request to /api/user, edit its path to /api/user/999 to test for IDOR vulnerabilities, and export the modified request as a curl command for your security report.

Frequently Asked Questions about caido-mode

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

FAQPage Schema
How do I replay HTTP requests with modified parameters without losing session cookies?

By using Caido's HTTP history and replay features via terminal commands, you can modify authenticated requests in-place. This preserves your session cookies and authentication tokens during security testing without manual copy-pasting.

What's the best way to test for IDOR vulnerabilities using saved HTTP history?

Locate an authenticated request in Caido's HTTP history, edit its user ID parameter to test for insecure direct object references, and export the modified request as a curl command. Authentication context is preserved automatically during IDOR testing.

Do I need Node.js to use Caido SDK commands for security testing?

Yes, executing CLI commands built on the @caido/sdk-client requires Node.js v24+. You also need a running Caido instance and a Personal Access Token to authenticate API requests for security testing.

Can I search HTTP history using HTTPQL directly from the terminal?

Yes, you can interact with all Caido features including HTTP history search via HTTPQL, replay session management, scope configuration, findings creation, and intercept control directly from the terminal using the Caido SDK.

Does this approach to authenticated request editing work for privilege escalation testing?

Yes, preserved auth request editing supports security testing workflows including privilege escalation, header bypass testing, and API reconnaissance. You modify existing authenticated requests without losing cookies or tokens during privilege escalation testing.

Why does manual token copy-pasting fail during API security testing?

Manual copy-pasting of large session cookies and authentication tokens introduces human error and breaks security testing workflows. In-place request modification with preserved authentication context eliminates this risk when testing authenticated web endpoints.