Insforge Integrations

This wires third-party auth providers (Clerk, Auth0, WorkOS, Kinde, Stytch, Better Auth) into InsForge for JWT-based row-level security, plus OKX as an x402 payment facilitator for onchain pay-per-use billing with USDG on X Layer. The auth side covers JWT claim injection and the `requesting_user_id()` RLS pattern. The payment side walks through 402 challenges, EIP-3009 signatures, and settling via OKX's verify/settle endpoints. Better Auth is notable because it runs in your own Postgres with no SaaS vendor or per-MAU cost. The guides are opinionated about common mistakes like using UUID columns for third-party user IDs or hardcoding JWT secrets instead of pulling them from the CLI.

skills.sh installs: 60.5K
GitHub stars: 47
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add insforge/insforge-skills --skill insforge-integrations --agent claude-code

Installs into .claude/skills of the current project.

Files

InsForge Integrations

This skill covers integrating third-party providers with InsForge. Currently two categories are supported: auth providers (RLS via JWT claims) and payment facilitators (x402 HTTP payment protocol). Each provider has its own guide under this directory.

Auth Providers

Provider	Guide	When to use
Clerk	Clerk JWT Templates + InsForge RLS	Clerk signs tokens directly via JWT Template — no server-side signing needed
Auth0	Auth0 Actions + InsForge RLS	Auth0 uses a post-login Action to embed claims into the access token
WorkOS	WorkOS AuthKit + InsForge RLS	WorkOS AuthKit middleware + server-side JWT signing with `jsonwebtoken`
Kinde	Kinde + InsForge RLS	Kinde token customization for InsForge integration
Stytch	Stytch + InsForge RLS	Stytch session tokens for InsForge integration
Better Auth	Better Auth + InsForge RLS	Self-hosted auth running in your InsForge Postgres — no third-party SaaS, no per-MAU cost