Clerk Security BasicsSAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-08Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: clerk-security-basics description: 'Implement security best practices with Clerk authentication. Use when securing your application, reviewing auth implementation, or hardening Clerk configuration. Trigger with phrases like "clerk security", "secure clerk", "clerk best practices", "clerk hardening". ' allowed-tools: Read, Write, Edit, Grep version: 1.15.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - clerk - security - authentication compatibility: Designed for Claude Code --- # Clerk Security Basics ## Overview Implement security best practices for Clerk authentication: environment variable protection, middleware hardening, API route defense, webhook verification, and session security. ## Prerequisites - Clerk SDK installed and configured - Understanding of OWASP authentication best practices - Production deployment planned or active ## Instructions ### Step 1: Secure Environment Variables ```bash # .env.local — never commit this file NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_live_... # Safe to expose (public) CLERK_SECRET_KEY=sk_live_... # NEVER expose client-side CLERK_WEBHOOK_SECRET=whsec_... # Server-only ``` ```gitignore # .gitignore — ensure secrets stay out of git .env.local .env.*.local .env.production ``` Validate at startup that secret keys are not leaked: ```typescript // lib/security-check.ts export function assertServerOnly() { if (typeof window !== 'undefined') { throw new Error('This module must only be used server-side') } if (!process.env.CLERK_SECRET_KEY) { throw new Error('CLERK_SECRET_KEY is not configured') } } ``` ### Step 2: Hardened Middleware Configuration ```typescript // middleware.ts import { clerkMiddleware, createRouteMatcher } from '@clerk/nextjs/server' import { NextResponse } from 'next/server' const isPublicRoute = createRouteMatcher([ '/', '/sign-in(.*)', '/sign-up(.*)', '/api/webhooks(.*)', ]) export default clerkMiddleware(async (auth, req) => { // Protect all non-public routes if (!isPublicRoute(req)) { await auth.protect() } // Add security headers const response = NextResponse.next() response.headers.set('X-Frame-Options', 'DENY') response.headers.set('X-Content-Type-Options', 'nosniff') response.headers.set('Referrer-Policy', 'strict-origin-when-cross-origin') response.headers.set( 'Content-Security-Policy', "frame-ancestors 'none'; form-action 'self' https://clerk.com https://*.clerk.accounts.dev" ) return response }) ``` ### Step 3: Secure API Routes ```typescript // app/api/admin/route.ts import { auth } from '@clerk/nextjs/server' import { NextRequest } from 'next/server' export async function POST(req: NextRequest) { const { userId, has } = await auth() // 1. Verify authentication if (!userId) { return Response.json({ error: 'Unauthorized' }, { status: 401 }) } // 2. Verify authorization (permission-based, not role-based) if (!has({ permission: 'org:admin:access' })) { return Response.json({ error: 'Forbidden' }, { status: 403 }) } // 3. Validate and sanitize input const body = await req.json() if (typeof body.name !== 'string' || body.name.length > 200) { return Response.json({ error: 'Invalid input' }, { status: 400 }) } // 4. Rate limit sensitive operations // (Use a rate limiter like @upstash/ratelimit) return Response.json({ success: true }) } ``` ### Step 4: Secure Webhook Verification ```typescript // app/api/webhooks/clerk/route.ts import { Webhook } from 'svix' import { headers } from 'next/headers' export async function POST(req: Request) { const secret = process.env.CLERK_WEBHOOK_SECRET if (!secret) { // Log but don't expose internal state console.error('Missing CLERK_WEBHOOK_SECRET') return new Response('Internal error', { status: 500 }) } const headerPayload = await headers() const svixHeaders = { 'svix-id': headerPayload.get('svix-id') || '', 'svix-timestamp': headerPayload.get('svix-timestamp') || '', 'svix-signature': headerPayload.get('svix-signature') || '', } // Reject requests missing required headers if (!svixHeaders['svix-id'] || !svixHeaders['svix-signature']) { return new Response('Missing verification headers', { status: 400 }) } const body = await req.text() const wh = new Webhook(secret) try { const event = wh.verify(body, svixHeaders) // Process verified event... return new Response('OK', { status: 200 }) } catch { // Don't leak verification details return new Response('Verification failed', { status: 400 }) } } ``` ### Step 5: Session Security Best Practices ```typescript // Enforce session checks in sensitive operations import { auth } from '@clerk/nextjs/server' export async function dangerousAction() { const { userId, sessionId } = await auth() if (!userId || !sessionId) { throw new Error('Valid session required') } // For extra-sensitive operations, verify the session is fresh // by checking session claims or requiring re-authentication const { sessionClaims } = await auth() const sessionAge = Date.now() / 1000 - (sessionClaims?.iat || 0) if (sessionAge > 300) { // 5 minutes throw new Error('Session too old for this operation. Please re-authenticate.') } } ``` Configure session settings in Clerk Dashboard: - **Session lifetime**: 7 days (default) — reduce for sensitive apps - **Inactivity timeout**: Enable for compliance requirements - **Multi-session mode**: Disable unless explicitly needed ## Output - Environment variables secured with leak prevention - Middleware with security headers (CSP, X-Frame-Options, etc.) - API routes with auth + authz + input validation - Webhook endpoint with Svix signature verification - Session freshness checks for sensitive operations ## Error Handling | Error | Cause | Solution | |-------|-------|----------| | Secret key exposed client-side | Impor
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__clerk-security-basics.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Clerk Security Basics skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Clerk Security Basics safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Clerk Security Basics access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Clerk Security Basics work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-08. The repository is watched, and a new audit runs when it changes — this is the first audit.