# Khaos Websocat Operations

> Use websocat only on an observed in-scope WebSocket endpoint; interpret its single-frame output as a connectivity probe, not an exploitation proof.

- Skill: `henriqqw/khaos-websocat-operations` (Agent Skill)
- Install (CLI): `npx get-skill add henriqqw/khaos-websocat-operations`
- Raw SKILL.md: https://api.skillmd.com/api/skills/henriqqw/khaos-websocat-operations/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: henriqqw (https://skillmd.com/u/henriqqw)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/henriqqw/khaos-websocat-operations

---


# Operacao do websocat no Khaos

O adapter Khaos para websocat executa uma unica conexao WebSocket, envia um frame JSON de ping, le uma resposta e encerra. Nao suporta streaming continuo, autenticacao OAuth, nem injecao de payloads personalizados.

## Pre-condicoes obrigatorias

- **Stage da task:** `vuln` ou `validation`.
- **Endpoint:** URL `ws://` ou `wss://` observada e confirmada como in-scope.
- **Estado do assessment:** `executing_stage`.
- O endpoint deve aceitar conexoes sem autenticacao por header ou deve ter tokens injetados via `auth_profiles` antes da execucao.

## Fluxo correto de execucao

```
1. POST /assessments/{id}/operator/tasks/{taskId}/claim
   {"owner": "<owner>", "lease_seconds": 180}

2. POST /assessments/{id}/operator/events
   {"event": "action_proposed", "data": {
     "action_id": "<uuid-novo>",
     "task_id":   "<taskId>",
     "owner":     "<owner>",
     "tool_id":   "websocat",
     "title":     "websocat probe: <wss://endpoint>"
   }}

3. POST /assessments/{id}/operator/events
   {"event": "action_decision", "data": {
     "action_id": "<mesmo-uuid>",
     "task_id":   "<taskId>",
     "owner":     "<owner>",
     "tool_id":   "websocat",
     "allowed":   true
   }}

4. POST /tools/websocat/run
   {"target_id": "<id>", "assessment_id": "<id>",
    "endpoint_url": "<wss://endpoint>",
    "execute": true, "confirm": true,
    "action_id": "<mesmo-uuid>", "task_id": "<taskId>", "owner": "<owner>"}
```

## O que o wrapper executa

Flags usadas pelo adapter: `--one-message --exit-on-eof --jsonlines --no-line-based <wsURL>`. O adapter converte automaticamente o esquema HTTP/HTTPS para WS/WSS.

## Interpretar sem superafirmar

| Resultado | Interpretacao |
|---|---|
| Frame de resposta recebido | Handshake bem-sucedido; verificar autenticacao e conteudo |
| Conexao recusada / timeout | Endpoint pode exigir auth ou nao estar ativo |
| Erro de protocolo | Endpoint nao WebSocket ou TLS incorreto |

Conectividade estabelecida nao implica vulnerabilidade. Use findings de WebSocket para investigar autenticacao fraca, injecao de mensagens e hijacking.

