- Home
- Skills
- APIs & Backend
- JWT Auth Safety Check
More screenshots
Works with the AI Agents you already use
JWT Auth Safety Check
One jwt.decode(token) where jwt.verify was meant, or one process.env.JWT_SECRET || 'secret', is enough for anyone to sign in as any user.
$5
JWT Auth Safety Check
Example session with this skill installed
Check this project with jwt-auth-safety-check.
- Read your context and instructions
- Compiled the jwt auth safety
$ python3 scripts/check_jwt.py examples/risky
BLOCK services/reports/auth.py:5 W03 ALGORITHM_CHOSEN_BY_TOKEN
return jwt.decode(token, public_key)
Why: The verifier lets the token choose its algorithm: PyJWT or python-jose decode with verification on but no algorithms list (python-jose and PyJWT 1.x then accept the algorithm named in the token; PyJWT 2.x raises DecodeError), algorithms=None, get_default_algorithms(), or a list built from the token's own header (header['alg']). This opens algorithm confusion: a token signed with HS256 using your public key as the HMAC secret can pass.
Safer: Pass a fixed list that matches your key, for example jwt.decode(token, key, algorithms=["RS256"]) or new Key($publicKey, 'RS256'). Never build it from the token header.
BLOCK src/auth/admin.js:5 W01 SIGNATURE_NOT_VERIFIED
BLOCK src/auth/tokens.js:4 W04 HARDCODED_SIGNING_KEY
BLOCK src/main/java/com/example/tokens/ServiceTokens.java:11 W02 NONE_ALGORITHM_ALLOWED
REVIEW package.json:9 W17 JWT_LIBRARY_WITH_KNOWN_FLAW
REVIEW services/reports/auth.py:12 W18 ALGORITHM_NOT_PINNED
REVIEW services/reports/auth.py:13 W14 EXPIRY_CHECK_OFF
REVIEW src/auth/sso.js:3 W15 AUDIENCE_OR_ISSUER_NOT_CHECKED
REVIEW src/auth/tokens.js:7 W11 NO_OR_LONG_EXPIRY
REVIEW src/auth/tokens.js:11 W16 TOKEN_IN_URL
REVIEW src/auth/tokens.js:13 W18 ALGORITHM_NOT_PINNED
REVIEW src/auth/tokens.js:21 W13 TOKEN_COOKIE_WITHOUT_FLAGS
REVIEW src/main/java/com/example/tokens/ServiceTokens.java:9 W11 NO_OR_LONG_EXPIRY
REVIEW web/src/session.js:2 W12 TOKEN_IN_BROWSER_STORAGE
REVIEW web/src/session.js:6 W16 TOKEN_IN_URL
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 7 files, 7 with JWT content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
One jwt.decode(token) where jwt.verify was meant, or one process.env.JWT_SECRET || 'secret', is enough for anyone to sign in as any user. This skill finds those and ten other JWT mistakes before you ship, and tells you how to fix each one.
Your agent runs a scanner on your JavaScript/TypeScript, Python, Go, Java, PHP and Ruby code and your dependency files. It knows the real APIs of jsonwebtoken, jose, PyJWT, python-jose, golang-jwt, jjwt, java-jwt, Nimbus, firebase/php-jwt and ruby-jwt, skips comments, strings and tests, and follows a key variable to its value in the same file. It does not flag normal verified use: jwt.verify with algorithms, PyJWT decode with algorithms and a key, ParseWithClaims with a key function that checks the signing method. It never runs your code. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- W01: tokens read without a signature check (jwt.decode, decodeJwt, verify_signature False, get_unverified_claims, ParseUnverified, java-jwt JWT.decode, JWT.decode(token, key, false), payloads base64-decoded by hand) in a function that never verifies the token
- W02: the none algorithm ('none' in an algorithm list, UnsecuredJWT, SigningMethodNone, Algorithm.none(), jjwt unsecured() and parseClaimsJwt, Nimbus PlainJWT)
- W03: the token picks the algorithm (PyJWT or python-jose decode without algorithms, get_default_algorithms(), header['alg'])
- W04: hard-coded signing keys, passed directly or through a variable such as $key = '...', and fallback secrets such as process.env.JWT_SECRET || 'dev-secret'
REVIEW
- W11: tokens with no expiry or one longer than 30 days
- W12: tokens in localStorage or sessionStorage
- W13: token and session cookies without HttpOnly, Secure or SameSite, and document.cookie tokens
- W14: ignoreExpiration, verify_exp off, skipped claims validation, leeway over 5 minutes
- W15: JWKS (SSO) tokens accepted without audience and issuer checks
- W16: tokens in URLs and query strings
- W17: jsonwebtoken before 9, PyJWT before 2.4.0, python-jose 3.3.0 or older, firebase/php-jwt before 6, golang-jwt before v4.5.2 / v5.2.2, dgrijalva/jwt-go
- W18: verify without a fixed algorithm list, golang-jwt key functions that never check the method, HS and RS mixed in one list
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason and safer approach for each rule
- A risky and a safe example project (Node API, browser client, Python service, Java service), and the real report the scanner produces on the risky one
Limits It reads code as text, not with a compiler: values are followed within one file, so keys or options defined in another file are not seen. Other JWT libraries (jwt-decode in the browser, lcobucci/jwt, Authlib, jwx, .NET) and lock files are not checked. NOT FLAGGED is not a guarantee.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Static check of code text. Values are followed within one file only; keys and options from other files, other JWT libraries and lock files are not checked. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes a clearly fake, inert secret (dev-secret-NOTREAL-EXAMPLE) for the scanner to find. It is never run.