insforge-integrations skill (InsForge): connect Clerk, Auth0 and more to InsForge

InsForge's own skill that has a coding agent connect Clerk, Auth0, WorkOS, Kinde, Stytch or Better Auth to InsForge, or add OKX x402 payments.

Installs: 57.9K; on skills.sh
Stars: 47; on GitHub
Files: 8; besides SKILL.md
Updated: Oct 2026; last repo commit

insforge-integrations makes your coding agent wire an outside sign-in provider into InsForge so row-level security works with that provider's user IDs. It has guides for Clerk, Auth0, WorkOS, Kinde, Stytch and Better Auth, and one for taking pay-per-use payments with the OKX x402 facilitator.

It loads when you connect one of those providers. The agent writes auth and JWT code, database policies and env vars in your project, and for x402 the code settles real payments onchain. Use the insforge skill for InsForge's built-in auth.

Good for

Developers building an app on InsForge's Postgres-based backend
Teams that already use Clerk, Auth0, WorkOS, Kinde or Stytch and want InsForge RLS to work with it
Developers who want self-hosted Better Auth running in their InsForge Postgres
Builders adding pay-per-use HTTP endpoints settled onchain with OKX x402

Install insforge-integrations

Claude Code

Copy this prompt.

Install the insforge-integrations skill in Claude Code. Run this command:

/plugin marketplace add InsForge/insforge-skills
/plugin install insforge@insforge

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Pick one route, not both. The skills CLI asks which skills to take: pick insforge-integrations. SKILL.md does not need the other three to run. The plugin route installs all 4. The skills run the InsForge CLI with npx, which needs Node.js 18 or newer, and you need an InsForge account and project. The README lists /install-skills under Claude Code. It is not a documented Claude Code built-in and we have not confirmed it works, so prefer the plugin or the skills CLI.

Built from the package data we hold. Not yet tested by us. Source.

What's in the skill

When it loads

Use when wiring an external auth provider (Clerk, Auth0, WorkOS, Kinde, Stytch, Better Auth) into InsForge for JWT-based RLS, or when adding the OKX x402 payment facilitator for onchain pay-per-use billing.

Sections in SKILL.md

Auth Providers
Payment Facilitators
Common Patterns
Auth providers
Payment facilitators (x402)
Choosing a Provider
Setup
Usage Examples
Best Practices
Common Mistakes

Key facts

Author: InsForge (vendor's own repo, README and plugin manifests)
License: Apache 2.0 (LICENSE file, README, SKILL.md and both plugin manifests agree)
Installs on skills.sh: 57,897 as of 2026-11-02
GitHub stars: 47 for the whole insforge-skills repo, 2026-11-02
What is inside: 9 files including SKILL.md: 7 provider guides (6 auth providers and OKX x402) plus agents/openai.yaml. It bundles no scripts.
Last change to this skill: 2026-08-04
Part of: The insforge plugin (4 skills) in the insforge marketplace
Needs: Node.js 18 or newer for @insforge/cli, run through npx, and an InsForge project

What it includes

JWT template, no server-side signing
Clerk signs the token through a JWT Template, and the client passes it to InsForge.
Write · Clerk
Post-login Action adds claims to the token
Uses an Auth0 Action to embed the claims InsForge needs in the access token.
Write · Auth0
AuthKit middleware and server-side JWT signing
Signs the token on the server with jsonwebtoken.
Write · WorkOS
Kinde token customization with server-side signing
Guide for Kinde and InsForge RLS.
Write · Kinde
Session tokens for InsForge
Guide for Stytch and InsForge RLS, with server-side session validation.
Write · Stytch
Self-hosted auth in your InsForge Postgres
No outside SaaS. SKILL.md says it needs a one-time REVOKE after migration to seal PostgREST exposure.
Runs code · Better Auth
Pay-per-use endpoints settled onchain in USDG
The server returns a 402 challenge, the client signs, and the server forwards to the facilitator's /verify and /settle. SKILL.md warns that settlement moves money before the database insert runs.
Write · OKX x402
requesting_user_id() and TEXT user_id columns
Auth provider IDs are strings, so SKILL.md says to use TEXT columns and requesting_user_id() instead of auth.uid(), and to get the JWT secret with secrets get JWT_SECRET.
Write · Common RLS pattern

From the official docs

Permissions

High risk

The agent writes sign-in and token-signing code, database policies and env vars, and the x402 guide handles real onchain payments. Review the code and test with mock mode and test accounts first.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

The x402 guide moves real money
SKILL.md warns that settlement takes money onchain before the database insert runs, and that MOCK_OKX_FACILITATOR=true returns fake transaction hashes and bypasses verification. Never leave mock mode on in production, and test with small amounts. github.com
It handles your JWT signing secret
The server-signing guides use the project's JWT secret. Keep it in server-only env vars and out of git. github.com
Wrong RLS setup can expose data or lock users out
Using auth.uid() or UUID columns with provider IDs breaks policies. Check the policies it writes against a test user before launch. github.com
The InsForge CLI sends usage events to PostHog
The CLI source says each command emits one PostHog event with non-sensitive properties, and uses an anonymous ID when no project is linked. The skill runs the CLI through npx, so those events come with it. github.com
The plugin route installs all 4 skills
The Claude and Codex plugin manifests cover the whole skills folder, which holds 4 skills, and the git tree has no hooks or MCP config. The Codex marketplace file sets authentication to ON_INSTALL. github.com
agents/openai.yaml holds interface settings
Each skill folder includes an agents/openai.yaml with a display name, short description, brand color and a default prompt. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details

Talks to	Your auth provider (Clerk, Auth0, WorkOS, Kinde, Stytch). OKX Web3 facilitator (x402 guide). api.insforge.dev and your InsForge project URL
Sign-in and keys	JWT signing secrets and provider keys end up in your env files. SKILL.md says to fetch the JWT secret from the CLI and never hardcode it.
Scopes	Writes auth, JWT-signing and RLS code in your project Runs npx -y @insforge/cli secrets get JWT_SECRET to read the signing secret Runs SQL migrations that create requesting_user_id() and RLS policies x402 code signs payment authorizations and calls the facilitator, which moves money onchain

Questions

What does the insforge-integrations skill do?

It guides your coding agent to connect a third-party sign-in provider to InsForge so row-level security uses that provider's user IDs. It covers Clerk, Auth0, WorkOS, Kinde, Stytch and Better Auth, plus the OKX x402 payment facilitator.

How do I install insforge-integrations?

Use the install box at the top of this page. insforge-integrations does not need the other InsForge skills to run, so with the skills CLI you can pick just it; the plugin route installs all 4. You also need Node.js 18 or newer and an InsForge account.

Which providers does it cover?

Six auth providers: Clerk, Auth0, WorkOS, Kinde, Stytch and Better Auth. The README adds OKX x402, which is a payment facilitator and not an auth provider.

Does it need an API key?

You need keys for the provider you connect, an InsForge project, and for x402 a Web3 API key from the OKX dev portal. SKILL.md says an OKX exchange trading key is the wrong kind.

Is insforge-integrations safe?

It writes auth and payment code that touches secrets and real money, so review it before you deploy. Use test accounts, and keep mock facilitator mode out of production.

Is this the official InsForge skill?

Yes. It is in InsForge's own insforge-skills repo, and the plugin manifests name InsForge as author.

insforge or insforge-integrations for auth?

Use insforge for InsForge's built-in auth. Use insforge-integrations only when you bring an outside provider such as Clerk or Auth0.

Information

updated Nov 2, 2026

Repository: insforge/insforge-skills
Folder: skills/insforge-integrations

insforge/insforge-skills skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 6

marketplace.json · github.com
README.md · github.com
README.md · github.com
plugin.json · github.com
SKILL.md · github.com
command-telemetry.ts · github.com