# Send JWT to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "jwt", "name": "JWT", "source": "tencent", "type": "skill", "category": "安全合规", "sourceUrl": "https://clawhub.ai/ivangdavila/jwt", "canonicalUrl": "https://clawhub.ai/ivangdavila/jwt", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/jwt", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=jwt", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md", "algorithms.md", "attacks.md", "lifecycle.md", "validation.md" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "jwt", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-29T08:37:03.289Z", "expiresAt": "2026-05-06T08:37:03.289Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=jwt", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=jwt", "contentDisposition": "attachment; filename=\"jwt-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "jwt" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/jwt" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/jwt", "downloadUrl": "https://openagent3.xyz/downloads/jwt", "agentUrl": "https://openagent3.xyz/skills/jwt/agent", "manifestUrl": "https://openagent3.xyz/skills/jwt/agent.json", "briefUrl": "https://openagent3.xyz/skills/jwt/agent.md" } } ``` ## Documentation ### Quick Reference TopicFileAlgorithm selectionalgorithms.mdToken lifecyclelifecycle.mdValidation checklistvalidation.mdCommon attacksattacks.md ### Security Fundamentals JWTs are signed, not encrypted—anyone can decode and read the payload; never store secrets in it Always verify signature before trusting claims—decode without verify is useless for auth The alg: none attack: reject tokens with algorithm "none"—some libraries accepted unsigned tokens Use strong secrets: HS256 needs 256+ bit key; short secrets are brute-forceable ### Algorithm Choice HS256 (HMAC): symmetric, same key signs and verifies—good for single service RS256 (RSA): asymmetric, private key signs, public verifies—good for distributed systems ES256 (ECDSA): smaller signatures than RSA, same security—preferred for size-sensitive cases Never let the token dictate algorithm—verify against expected algorithm server-side ### Required Claims exp (expiration): always set and verify—tokens without expiry live forever iat (issued at): when token was created—useful for invalidation policies nbf (not before): token not valid until this time—for scheduled access Clock skew: allow 30-60 seconds leeway when verifying time claims ### Audience & Issuer iss (issuer): who created the token—verify to prevent cross-service token theft aud (audience): intended recipient—API should reject tokens for other audiences sub (subject): who the token represents—typically user ID Token confusion attack: without aud/iss validation, token for Service A works on Service B ### Token Lifecycle Access tokens: short-lived (5-15 min)—limits damage if stolen Refresh tokens: longer-lived, stored securely—used only to get new access tokens Refresh token rotation: issue new refresh token on each use, invalidate old one Revocation is hard—JWTs are stateless; use short expiry + refresh, or maintain blacklist ### Storage httpOnly cookie: immune to XSS, but needs CSRF protection localStorage: vulnerable to XSS, but simpler for SPAs Memory only: most secure, but lost on page refresh Never store in URL parameters—visible in logs, history, referrer headers ### Validation Checklist Verify signature with correct algorithm (don't trust header's alg) Check exp is in future (with clock skew tolerance) Check iat is not unreasonably old (optional policy) Verify iss matches expected issuer Verify aud includes your service Check nbf if present ### Common Mistakes Storing sensitive data in payload—it's just base64, not encrypted Huge payloads—JWTs go in headers; many servers limit header size to 8KB No expiration—indefinite tokens are security nightmares Same secret across environments—dev tokens work in production Logging tokens—they're credentials; treat as passwords ### Key Rotation Use kid (key ID) claim to identify which key signed the token JWKS (JSON Web Key Set) endpoint for public key distribution Overlap period: accept old key while transitioning to new After rotation, old tokens still valid until they expire—plan accordingly ### Implementation Use established libraries—don't implement JWT parsing yourself Libraries: jsonwebtoken (Node), PyJWT (Python), java-jwt (Java), golang-jwt (Go) Middleware should reject invalid tokens early—before any business logic ## Trust - Source: tencent - Verification: Indexed source record - Publisher: ivangdavila - Version: 1.0.1 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-04-29T08:37:03.289Z - Expires at: 2026-05-06T08:37:03.289Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/jwt) - [Send to Agent page](https://openagent3.xyz/skills/jwt/agent) - [JSON manifest](https://openagent3.xyz/skills/jwt/agent.json) - [Markdown brief](https://openagent3.xyz/skills/jwt/agent.md) - [Download page](https://openagent3.xyz/downloads/jwt)