agentleFS
Lethe044Lethe044/agentskill-kit/skills/jwt-inspector/SKILL.md

jwt-inspector

Skill50 starsChanged 21 days agoMITView on GitHub

Decodes a JSON Web Token without verifying it, shows the header and claims with readable dates and flags risks such as alg none, a missing expiry, an expired token or a very long lifetime. Use when the user pastes a JWT and asks what is inside, why a token is rejected, or whether its settings look safe.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not store tokens in files or logs while debugging.

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

JWT inspector

Reads a token the way a debugger would. It never verifies the signature and never prints it.

When to use

  • The user pastes a token and asks what the claims say.
  • An API answers 401 and the user suspects the token has expired or is not valid yet.
  • A review needs a quick check of algorithm, expiry and lifetime.

How to run

python scripts/inspect_jwt.py "eyJhbGciOi..."
echo "$TOKEN" | python scripts/inspect_jwt.py
python scripts/inspect_jwt.py "$TOKEN" --now 1700000000

A leading Bearer is ignored. --now takes epoch seconds or an ISO time ending in Z and makes results repeatable.

Output

JSON with header, payload, alg, typ, the times issued_at, not_before and expires_at (UTC), expired (true, false or null when there is no expiry), lifetime_seconds and warnings.

Possible warnings: the algorithm is none, the signature is empty, there is no exp claim, the lifetime is longer than 24 hours, the token is expired, the token is not valid yet.

Safety

  • Decoding is not verification. Anyone can create a token with any claims. Never use this output to decide whether to trust a token.
  • Tokens are credentials. Tell the user to treat a pasted token as exposed if it is still valid, and to rotate it.
  • Do not store tokens in files or logs while debugging.

Errors

A value that is not a three part token with JSON header and payload exits with code 3.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.