api-security-auth-pattern

api-security-auth-pattern is a skill for Claude Code, Codex from LambdaTest/agent-skills. It costs 166 tokens per session (1,359 once invoked), scanned A, original, MIT.

A tool for designing API authentication, authorization, and security patterns. Authentication checks who is calling an API, while authorization controls what that caller may do.

In plain words
What is it for?
Planning OAuth 2.0, JWT, API-key, mTLS, webhook-signature, RBAC, ABAC, CORS, HTTPS, input-validation, rate-limit, and multi-tenant isolation patterns.
Why use it?
It helps choose and document suitable security flows instead of piecing together tokens, permissions, and request protections manually. It covers common API security concerns and their supporting endpoints.

Skill for Claude CodeCodex

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/lambdatest/agent-skills/api-security-patterns
Any agent
npx skills add LambdaTest/agent-skills --skill api-security-patterns
Clone the repo
git clone --depth 1 https://github.com/LambdaTest/agent-skills

Made for: Claude Code, Codex.

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 api-security-auth-pattern

README.md
[![agentmods](https://agentmods.dev/badge/skills/lambdatest/agent-skills/api-security-patterns.svg)](https://agentmods.dev/skills/lambdatest/agent-skills/api-security-patterns)
Your own site
<a href="https://agentmods.dev/skills/lambdatest/agent-skills/api-security-patterns"><img src="https://agentmods.dev/badge/skills/lambdatest/agent-skills/api-security-patterns.svg" alt="Measured on agentmods" height="20"></a>
Per session 166 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,359 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.00166 $0.01359
Opus 5 $0.00083 $0.00679
Sonnet 5 $0.00033 $0.00272
Haiku 4.5 $0.00017 $0.00136

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

Security

Grade A, and why

api-security-auth-pattern 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 3d 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.

api-skill/api-security-patterns/SKILL.md · 176 lines

How it starts

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

API Security & Auth Skill

Design complete authentication and security layers for any API.


Auth Pattern Selection Guide

Use Case Recommended Pattern
User-facing web/mobile app OAuth 2.0 + JWT (Authorization Code + PKCE)
Server-to-server (M2M) OAuth 2.0 Client Credentials + JWT
Simple 3rd party access API Key (header)
High-security enterprise mTLS + short-lived JWT
Microservices internal JWT propagation or service mesh (mTLS)
Webhook verification HMAC-SHA256 signature header

OAuth 2.0 Flow Endpoints

POST /auth/oauth/authorize      — redirect user to consent screen
POST /auth/oauth/token          — exchange code for tokens
POST /auth/oauth/token/refresh  — refresh access token
POST /auth/oauth/revoke         — revoke token
GET  /auth/oauth/userinfo       — get user profile from token

Token endpoint request

{
  "grant_type": "authorization_code",
  "code": "AUTH_CODE",
  "redirect_uri": "https://app.example.com/callback",
  "client_id": "CLIENT_ID",
  "code_verifier": "PKCE_VERIFIER"
}

Token response

{
  "access_token": "eyJhbGci...",
  "token_type": "Bearer",
  "expires_in": 3600,
  "refresh_token": "rt_...",
  "scope": "read write"
}

JWT Design

Header: { "alg": "RS256", "typ": "JWT" }

Claims payload:

{
  "sub": "user-uuid",
  "iss": "https://auth.example.com",
  "aud": "https://api.example.com",
  "exp": 1700000000,
  "iat": 1699996400,
  "jti": "unique-token-id",
  "roles": ["admin", "editor"],
  "tenant_id": "org-uuid",
  "scope": "read:users write:posts"
}

Validation checklist: verify iss, aud, exp, nbf; reject alg: none; check token revocation list.


RBAC Design

Roles:   super_admin > admin > editor > viewer > guest
Resources: users, posts, settings, billing, reports

Permission matrix:
              users   posts  settings  billing  reports
super_admin:  CRUD    CRUD   CRUD      CRUD     R
admin:        CRUD    CRUD   R         R        R
editor:       R       CRUD   -         -        R
viewer:       R       R      -         -        R
guest:        -       R(pub) -         -        -

Read the full file on GitHub · 176 lines

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. 3d ago First seen · 176 lines · 166 tokens per session scan A bf8405bc4c3e

Subscribe to this mod's changes

api-security-auth-pattern is a skill published in the GitHub repository LambdaTest/agent-skills (365 stars, last pushed 1mo ago), licensed MIT. It adds 166 tokens to every session and 1,359 once invoked, about $0.0008 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.

Related

Other skills, from other repositories

keploy-docs

Guide for contributing to the Keploy documentation site at github.com/keploy/docs. Invoke when a change in keploy/keploy introduces, removes, or alters user-visible behavior (new CLI flag, changed default, new command, new configuration field, new on-disk format) and the docs need to catch up — or when the user asks…

keploy/keploy · 116 tokens

keploy-pr-workflow

Guide for creating PRs and issues on keploy repositories — PR format, customer-data hygiene, commit conventions, sign-off. Invoke when the user asks to open, update, or review a pull request or issue, when preparing a commit that will land in main, or whenever a change is about to leave the local machine.

keploy/keploy · 71 tokens

keploy-e2e-test

End-to-end verification of a change to keploy/keploy using keploy's own record/replay against a real sample application. Use whenever the user asks to test a change, verify a fix, prove that a modification works in practice, add e2e coverage for a PR, reproduce a bug against a sample app, or wire a behavior into CI.…

keploy/keploy · 118 tokens

detecting-broken-object-property-level-authorization

Detect and test for OWASP API3:2023 Broken Object Property Level Authorization vulnerabilities including excessive data exposure and mass assignment attacks.

xalgorix/xalgorix · 36 tokens

API Test Suite Generator

Automatically generate comprehensive API test suites from OpenAPI specifications covering CRUD operations, error handling, authentication, pagination, and edge cases.

PramodDutta/qaskills · 29 tokens

api-testing

API testing patterns for Playwright -- apiRequest fixture usage, Zod response schema creation and validation, test.step wrapping for multi-call tests, per-field negative/validation testing, path parameter fuzzing, and helper fixtures for shared setup/teardown. Use when writing or updating API test specs, adding tests…

idavidov13/agentic-playwright · 132 tokens