A procedure for creating JSON Web Tokens (JWTs), which are signed credentials used to authenticate requests to a service.

Use it to create a user's token with an expiry time and, when needed, attach a request ID, allowed IP addresses, service name, or other key-value data.

It ensures required details such as the username and token lifetime are collected before access credentials are issued.

How Bazilio-san/mcp-vkusvill configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Bazilio-san/mcp-vkusvill. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Bazilio-san/mcp-vkusvill/master/.claude/skills/gen-jwt/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/Bazilio-san/mcp-vkusvill

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bazilio-san/mcp-vkusvill/gen-jwt/github.svg)](https://agentmods.dev/skills/bazilio-san/mcp-vkusvill/gen-jwt)

Your own site

<a href="https://agentmods.dev/skills/bazilio-san/mcp-vkusvill/gen-jwt"><img src="https://agentmods.dev/badge/skills/bazilio-san/mcp-vkusvill/gen-jwt/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bazilio-san/mcp-vkusvill/gen-jwt"><img src="https://agentmods.dev/badge/skills/bazilio-san/mcp-vkusvill/gen-jwt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,480 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00045	$0.01480
Opus 5.5	$0.00018	$0.00592
Sonnet 5.5	$0.00009	$0.00296
Haiku 4.5	$0.00005	$0.00148

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

Security

Grade A, and why

gen-jwt 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

gen-jwt — 92% identical, 17 lines differ

.claude/skills/gen-jwt/SKILL.md · 113 lines

How it starts

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

JWT Token Generator

Generate a JWT token by running node scripts/generate-jwt.js with the appropriate parameters.

Parameter Extraction

Parse $ARGUMENTS and the user's request to extract:

username (REQUIRED) — the user the token is issued to
ttl (REQUIRED) — token lifetime in format <N>s | <N>m | <N>d | <N>y (seconds, minutes, days, years)
request (optional) — ticket/issue ID if user mentions "заявка", "тикет", "ticket", "request", "issue", "REQ-", "JIRA-" etc. The param key is always request
ip (optional) — allowed IP addresses/CIDR masks, comma-separated
service (optional) — service name, passed via -s
extra params (optional) — any other key=value pairs

Interactive Flow

Step 1: Validate required params

If username is missing or empty:

Tell the user: "Username is required. Please specify the user the token should be issued to."
Wait for response. Do not proceed without it.

If ttl is missing, not provided, or doesn't match <N>s | <N>m | <N>d | <N>y:

Tell the user: "Token lifetime (TTL) is required in format: <N>s (seconds), <N>m (minutes), <N>d (days), or <N>y (years). For example: 30d, 1y, 8d. Please specify."
Wait for response. Do not proceed without a valid TTL.

Step 2: Ask about optional params (only if not already provided)

If the user did NOT mention a request/ticket:

Ask: "Привязать к заявке? (введите ID заявки или Enter чтобы пропустить)"
If user says "no", "skip", "нет", "-", or presses Enter — omit the request param.

If the user did NOT mention IP restrictions:

Ask: "Ограничить по IP? (введите IP/CIDR через запятую или Enter чтобы пропустить)"
If user says "no", "skip", "нет", "-", or presses Enter — omit the ip param.

Step 3: Build and run the command

Construct the CLI command:

node scripts/generate-jwt.js -u <username> -ttl <ttl> [-s <service>] [-p "<params>"]

The -p value is a semicolon-separated string of key=value pairs built from:

request=<ticket> (if provided)
ip=<addresses> (if provided)
Any extra key=value pairs from the user's message

Read the full file on GitHub · 113 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.

2mo ago First seen · 113 lines · 45 tokens per session scan A 27d99a1f10ce

Subscribe to this mod's changes

gen-jwt is a skill published in the GitHub repository Bazilio-san/mcp-vkusvill (1 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 1,480 once invoked, about $0.0002 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-31.