Backend Validation

Hurl + websocat + oauth2c workflow for validating OIDC-authenticated backend APIs and WebSockets.

Door johnkozaris · johnkozaris/jko-claude-plugins

Getest · Werkt ★ 8.8/10

Backend Validation — Hurl + websocat + oauth2c workflow for validating OIDC-authenticated backend APIs and WebSockets.

Wat het doet

Provides a disciplined CLI workflow for validating backend REST/WebSocket endpoints end-to-end, including OIDC token acquisition via oauth2c with refresh-token caching in OS-native secret storage. Triggers when a user wants to smoke-test an API, write a Hurl regression test, debug a 401, or hit an authenticated WebSocket, and explicitly steps aside when a project already uses Postman/Bruno or the endpoint has no auth.

Testrapport

Ran the actual A/B: a hand-written curl+jq bash validator vs. the skill's Hurl file with [Captures]/[Asserts], both executed live against a throwaway local HTTP server — the Hurl version is roughly half the code, declaratively chains the session id, and its companion token-script.sh sidesteps the ROPC failure mode the skill warns about (public PKCE clients reject password grant against real IdPs like Authentik).

Getest op: 2026-07-15 · Claude Code 2.x (agent harness)

Installatie

git clone https://github.com/johnkozaris/jko-claude-plugins
mkdir -p ~/.claude/skills
cp -r jko-claude-plugins/plugins/backend-validator/skills/backend-validation ~/.claude/skills/backend-validation

Commando's en voorbeeldprompts

/backend-validationHurl + websocat + oauth2c workflow for validating OIDC-authenticated backend APIs and WebSockets.

Skills reageren op gewone verzoeken — geen commando's om te onthouden. Na installatie activeren prompts zoals deze de skill (in het Engels):

write a regression test that hits my OIDC-protected API endpoint
help me debug why my API keeps returning 401 with this bearer token
smoke test this authenticated websocket connection end to end

Volledig rapport (Engels) →