insforge-integrations

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.

17stars6forksUpdated 5/8/2026

Security Database Management #security #agent #database #integrations #insforge

Security Assessment

Critical Risk(20/100)

Detected risks:

Data Exfiltration([references/okx-x402.md] fetch(OKX_BASE + "/verify", { method: "POST", headers: okxHeaders("POST, [references/okx-x402.md] fetch(OKX_BASE + "/settle", { method: "POST", headers: okxHeaders("POST, [references/okx-x402.md] fetch(path, { method: "POST)

Secret Exposure([references/auth0.md] Token =, [references/better-auth.md] token =, [references/better-auth.md] Token =)

Sensitive File Access([references/auth0.md] .env, [references/better-auth.md] .env, [references/clerk.md] .env)

Security Score20/100

About insforge-integrations

insforge-integrations is a reusable AI skill focused on a specific workflow. name: insforge-integrations

The skill packages instructions, conventions, and task-specific guidance so an agent can execute the job more consistently. 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.

In practice, this skill is best suited for users who need repeatable execution with fewer setup steps and less ambiguity. organization: InsForge 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. | Provider | Guide | When to use | |----------|-------|-------------|

FAQ

What does insforge-integrations help with?

insforge-integrations helps agents follow a focused workflow described in the source documentation, reducing ambiguity and keeping execution aligned with the intended task.

When should this skill be used?

Use it when the task matches the workflow, domain, or operating rules described in the skill documentation, especially when consistent execution matters.

What are the main limitations?

The skill is constrained by the quality and scope of its source instructions. If the underlying documentation is incomplete, the agent may still need extra context or manual validation.