CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

offensive-jwt

JWT attack methodology for penetration testers. Covers algorithm confusion (alg:none, RS256→HS256), weak HMAC secret brute force, kid parameter injection (SQLi, path traversal), jku/x5u/jwk header injection, JWKS cache poisoning, JWS/JWE confusion, timing attacks, and mobile JWT storage extraction. Use when testing JWT-based authentication, hunting auth bypass via token manipulation, or evaluating JWT implementation security in web or mobile apps.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./Skills/auth/offensive-jwt/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, technically credible attack checklist with genuinely actionable commands and payloads, undermined by systematic redundancy (the same vulnerability list appears four times), no verification checkpoints in the testing workflow, and a monolithic single-file structure that should offload mobile, remediation, and alternatives detail to reference files.

Suggestions

Consolidate the redundant vulnerability enumerations: the Quick Reference bullets, the Vulnerability Map ASCII tree, and the Vulnerabilities section all restate the same class list — keep one map and let the detailed sections carry the specifics.

Add validation checkpoints to the Manual Testing Steps (e.g., after each technique, what response signature indicates success — HTTP status deltas, signature-accepted vs rejected behaviors — and when to re-test with a modified payload).

Move the Mobile App JWT Storage, Remediation Recommendations, and Alternatives & Modern Mitigations sections into reference files (e.g., references/mobile-extraction.md, references/remediation.md) and link them from a short overview, keeping SKILL.md itself a lean checklist.

DimensionReasoningScore

Conciseness

The same vulnerability classes are repeated across four sections (Quick Reference bullets, the Vulnerability Map tree, the Vulnerabilities section, and Manual Testing Steps), and the Mechanisms section explains basics like 'JWTs (RFC 7519) consist of three Base64URL-encoded parts' that Claude already knows. Mostly efficient but could be tightened significantly by consolidating.

3 / 5

Actionability

Mostly executable guidance with copy-paste-ready commands ('python3 jwt_tool.py <token> -M all', 'adb shell "run-as com.target.app cat ..."', concrete kid/jwk/jku header payloads). Minor gaps: step 1 is pseudocode ('base64url_decode(header).payload.signature') and the timing-attack script needs target adaptation.

4 / 5

Workflow Clarity

'Follow steps in order' plus the ordered Hunt and Manual Testing Steps give a clear sequence, but validation checkpoints are entirely absent — there is no guidance on how to confirm a technique succeeded (response differences, error signatures, re-testing).

3 / 5

Progressive Disclosure

No bundle files exist and the entire ~280-line body is inlined in SKILL.md. Section headers are clear, but content that belongs in separate reference files (mobile storage extraction detail, remediation recommendations, alternatives/modern mitigations) is inlined, and the file far exceeds the 50-line simple-skill case.

3 / 5

Total

13

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: specific, third-person, comprehensive on capabilities, with an explicit and well-phrased 'Use when' trigger clause. The only weakness is missing a few natural synonyms (e.g., 'JSON Web Token', 'bearer token') in the trigger terms.

DimensionReasoningScore

Specificity

Enumerates eight concrete techniques — 'algorithm confusion (alg:none, RS256→HS256)', 'kid parameter injection (SQLi, path traversal)', 'JWKS cache poisoning', 'timing attacks', 'mobile JWT storage extraction' — in third-person voice, comprehensively covering the JWT attack surface.

5 / 5

Completeness

Explicitly answers both 'what' (the enumerated technique coverage) and 'when' ('Use when testing JWT-based authentication, hunting auth bypass via token manipulation, or evaluating JWT implementation security in web or mobile apps') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keywords ('JWT', 'auth bypass', 'token manipulation', 'web or mobile apps') that users would actually say, but misses common synonyms like 'JSON Web Token' and 'bearer token'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (offensive JWT testing) with distinct triggers; minimal risk of firing for unrelated auth or web-security skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

SnailSploit/Claude-Red

Path

Skills/auth/offensive-jwt/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.