jwt-auth-setup

jwt-auth-setup is a skill for Claude Code from StefanTheCode/dotnet-ai-toolkit. It costs 99 tokens per session (1,321 once invoked), scanned A, original, MIT.

A guide for setting up JWT authentication and authorization in an ASP.NET Core API. JWTs are signed tokens that carry information about a logged-in user; authorization decides which users may access each endpoint.

In plain words
What is it for?
Use it to add or review login-token issuing, bearer-token validation, refresh tokens, claims, roles, authorization policies, and endpoint protection.
Why use it?
It helps protect API routes and avoid common mistakes in token validation, signing-key storage, HTTPS requirements, refresh tokens, and access policies. It can also review an existing setup instead of adding a second one.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the dotnet-ai-toolkit plugin — 49 skills shipped together

Good fit Use it to add or review login-token issuing, bearer-token validation, refresh tokens, claims, roles, authorization policies, and endpoint protection.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/stefanthecode/dotnet-ai-toolkit/jwt-auth-setup
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.

Any agent
npx skills add StefanTheCode/dotnet-ai-toolkit --skill jwt-auth-setup
Clone the repo
git clone --depth 1 https://github.com/StefanTheCode/dotnet-ai-toolkit

Made for: Claude Code.

Or install dotnet-ai-toolkit, the plugin that ships this one along with the rest of its 49 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 jwt-auth-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/stefanthecode/dotnet-ai-toolkit/jwt-auth-setup/github.svg)](https://agentmods.dev/skills/stefanthecode/dotnet-ai-toolkit/jwt-auth-setup)
Your own site
<a href="https://agentmods.dev/skills/stefanthecode/dotnet-ai-toolkit/jwt-auth-setup"><img src="https://agentmods.dev/badge/skills/stefanthecode/dotnet-ai-toolkit/jwt-auth-setup/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for jwt-auth-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/stefanthecode/dotnet-ai-toolkit/jwt-auth-setup"><img src="https://agentmods.dev/badge/skills/stefanthecode/dotnet-ai-toolkit/jwt-auth-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 99 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,321 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Privilege Escalation · line 90
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • high Privilege Escalation · line 102
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • high Privilege Escalation · line 100
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
How audits are shown
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.1 $0.00099 $0.01321
Opus 5.5 $0.00040 $0.00528
Sonnet 5.5 $0.00020 $0.00264
Haiku 4.5 $0.00010 $0.00132

Measured 2mo ago against content hash e865d45f63b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

jwt-auth-setup 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 2mo 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/jwt-auth-setup/SKILL.md · 143 lines

How it starts

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

JWT Auth Setup (ASP.NET Core)

Wire up JWT bearer authentication and authorization in an ASP.NET Core API with secure defaults: token issuing, validation, refresh tokens, and policy-based authorization.

Input — point it at your project

If they point at a project or repo, inspect the existing auth setup before changing anything:

  • A project or repo root — find the auth wiring and review it.
  • A GitHub URL — clone first, then inspect: git clone --depth 1 <url> /tmp/repo && cd /tmp/repo

Discover current state yourself, e.g.:

grep -rn "AddAuthentication\|AddJwtBearer\|TokenValidationParameters\|AddAuthorization\|RequireAuthorization\|RequireHttpsMetadata" --include=*.cs <target> | grep -vi "/obj/\|/bin/"

If auth already exists, review and harden it (validation flags, HTTPS metadata, ClockSkew, refresh-token handling, where the signing key lives) rather than re-adding from scratch, and flag any access-control gaps (endpoints without RequireAuthorization / no fallback policy).

When this runs

The user wants to secure an API with JWTs, or wants their existing auth reviewed. If new: confirm whether they're issuing tokens themselves (own login) or validating tokens from an external IdP (Azure AD / Auth0 / Keycloak). Defaults below cover self-issued; for external IdP, the validation half is the same and issuing is delegated.

Packages

dotnet add package Microsoft.AspNetCore.Authentication.JwtBearer
dotnet add package System.IdentityModel.Tokens.Jwt

Validation wiring (Program.cs)

var jwt = builder.Configuration.GetSection("Jwt");

builder.Services.AddAuthentication(JwtBearerDefaults.AuthenticationScheme)
    .AddJwtBearer(options =>
    {
        options.TokenValidationParameters = new TokenValidationParameters
        {
            ValidateIssuer = true,
            ValidateAudience = true,
            ValidateLifetime = true,
            ValidateIssuerSigningKey = true,
            ValidIssuer = jwt["Issuer"],
            ValidAudience = jwt["Audience"],
            IssuerSigningKey = new SymmetricSecurityKey(
                Encoding.UTF8.GetBytes(jwt["Key"]!)),
            ClockSkew = TimeSpan.FromSeconds(30) // tighten the default 5 min
        };
    });

builder.Services.AddAuthorization(options =>
{
    options.AddPolicy("AdminOnly", p => p.RequireRole("Admin"));
    options.AddPolicy("CanManageOrders", p => p.RequireClaim("permission", "orders:manage"));
});

// ... after build:
app.UseAuthentication();
app.UseAuthorization();

Read the full file on GitHub · 143 lines

Files

What ships with it

1 file 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. 2mo ago First seen · 143 lines · 99 tokens per session scan A e865d45f63b0

Subscribe to this mod's changes

jwt-auth-setup is a skill published in the GitHub repository StefanTheCode/dotnet-ai-toolkit (26 stars, last pushed 2mo ago), licensed MIT. It adds 99 tokens to every session and 1,321 once invoked, about $0.0004 per session on Opus 5.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

jwt-auth-setup compared with skills from other repositories

jwt-auth-setup next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
jwt-auth-setupStefanTheCode/dotnet-ai-toolkitSkill262mo agoMITA99Claude Code
mem0-oss-to-platformmem0ai/mem0Skill68k2d agoApache-2.0A217Claude Code, Codex
azure-mgmt-botservice-dotnetmicrosoft/skillsSkill3.2kyesterdayMITA78Claude Code
fastapi-router-pymicrosoft/skillsSkill3.2kyesterdayMITA46Claude Code
dev-runtimelangwatch/langwatchSkill5.0kyesterdayApache-2.0A172Claude Code
api-designericrisco/rsc-harnessSkill5032d agoMITA105Claude Code, Codex
migrate-segw-to-raparc-mcp/arc-1Skill252yesterdayMITA106Claude Code