insforge-integrations

insforge-integrations is a skill for Claude Code, Codex from InsForge/insforge-skills. It costs 59 tokens per session (1,448 once invoked), scanned A, original, Apache-2.0.

Integration guides for connecting external sign-in services and an online payment service to InsForge, a backend platform. They cover sending login information in JWT tokens so InsForge can control database access, plus x402 pay-per-use payments.

In plain words
What is it for?
Use it when adding Clerk, Auth0, WorkOS, Kinde, Stytch, or Better Auth to InsForge, or when adding OKX’s x402 payment facilitator for onchain pay-per-use billing.
Why use it?
They explain how to connect these providers without having to work out each provider’s token and payment setup from scratch. This helps applications recognise users, apply database access rules, and charge for HTTP requests.

Skill for Claude CodeCodex

Part of the insforge plugin — 4 skills shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/insforge/insforge-skills/insforge-integrations
Any agent
npx skills add InsForge/insforge-skills --skill insforge-integrations
Clone the repo
git clone --depth 1 https://github.com/InsForge/insforge-skills

Made for: Claude Code, Codex.

Or install insforge, the plugin that ships this one along with the rest of its 4 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for insforge-integrations

README.md
[![agentmods](https://agentmods.dev/badge/skills/insforge/insforge-skills/insforge-integrations.svg)](https://agentmods.dev/skills/insforge/insforge-skills/insforge-integrations)
Your own site
<a href="https://agentmods.dev/skills/insforge/insforge-skills/insforge-integrations"><img src="https://agentmods.dev/badge/skills/insforge/insforge-skills/insforge-integrations.svg" alt="Measured on agentmods" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,448 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00059 $0.01448
Opus 5 $0.00030 $0.00724
Sonnet 5 $0.00012 $0.00290
Haiku 4.5 $0.00006 $0.00145

Measured 5d ago against content hash 86e9f0ebecff, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

insforge-integrations scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/insforge-integrations/SKILL.md · 107 lines

How it starts

The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

Payment Facilitators

Provider Guide When to use
OKX x402 OKX as x402 facilitator (USDG on X Layer) Pay-per-use HTTP endpoints settled onchain with zero gas for the payer

Common Patterns

Auth providers

  1. Provider signs or issues a JWT containing the user's ID
  2. JWT is passed to InsForge via accessToken in createClient() (deprecated alias: edgeFunctionToken)
  3. InsForge exposes claims through auth.jwt() in SQL
  4. RLS policies use a requesting_user_id() function to enforce row-level security

Payment facilitators (x402)

  1. Server returns 402 Payment Required with a JSON challenge base64-encoded in PAYMENT-REQUIRED header
  2. Client signs an EIP-3009 authorization using the stablecoin's EIP-712 domain
  3. Server forwards the signed payload to the facilitator's /verify + /settle endpoints
  4. Server records the settled payment in an InsForge table with a realtime trigger for live dashboards

Read the full file on GitHub · 107 lines

Files

What ships with it

8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 107 lines · 59 tokens per session scan A 86e9f0ebecff

Subscribe to this mod's changes

insforge-integrations is a skill published in the GitHub repository InsForge/insforge-skills (36 stars, last pushed 7d ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,448 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.