Caido Mode provides extensive CLI commands and patterns for interacting with a Caido instance via the official @caido/sdk-client. It enables HTTP history search (HTTPQL), replay and edit of requests (preserving auth), session and collection management, scope/filter presets, environment variables for tests, findings creation, fuzzing automation and export-to-curl for PoCs. The skill documents recommended auth setup, CLI usage, and important safety notes (don’t dump raw requests into context).
Use when investigating or testing web traffic captured by Caido: replaying real requests, creating PoCs, fuzzing, or creating findings. It's aimed at security workflows where maintaining original auth context and precise HTTPQL queries matters.
caido-client.ts and command examples (has_scripts=false in fetch but sibling files include CLI source)Agents that can run Node/TS toolchains or execute CLI steps (Claude Code, Node-enabled agents, or local agent runtimes) will benefit most.
Caido Mode is a comprehensive CLI skill for Caido's web security testing platform, providing HTTP history search, request replay/editing, scope management, findings creation, and intercept control via the official @caido/sdk-client. No bundled scripts were present for runtime testing. The SKILL.md is thorough with clear command examples, workflow patterns, and SDK architecture documentation. Auth uses PAT stored in secrets.json — reasonable for a security tool. The skill targets a niche audience (Caido web security testing users) but delivers deep integration for that audience.
Well-documented security testing skill with clear architecture. The skill uses official SDK (no raw fetch), has proper auth flow with token caching, and good error handling guidance. Security deductions: PAT token storage in secrets.json (-8), network calls to user's own Caido instance are expected for this tool but still network activity (-5), the skill instructs modifying auth headers and removing CSRF tokens which is the point of a security testing tool but could be misused (-5). No hardcoded credentials, no curl|bash, no exfiltration. Architecture is strong — multi-file SDK structure with clear separation of concerns. Usefulness is limited by Caido's niche audience but very high for that audience.