auth-analyzer
Analyze Authentication Security
Authentication and authorization bugs can expose accounts, sessions, and private data. This skill guides Claude, Codex, and Claude Code through focused auth reviews with clear remediation advice.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "auth-analyzer" from https://skillstore.io/skills/curiouslearner-auth-analyzer.md and its manifest at https://skillstore.io/api/skills/curiouslearner-auth-analyzer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "auth-analyzer". Review a login route that stores MD5 password hashes and returns different errors for unknown users.
Expected outcome:
- Critical finding: weak password hashing exposes users if the database is leaked.
- Medium finding: different login errors can reveal whether an account exists.
- Recommended fix: migrate to Argon2id, use uniform error messages, and add rate limiting.
Using "auth-analyzer". Check an API route where authenticated users can update any user ID in the URL.
Expected outcome:
- High finding: missing ownership check allows horizontal privilege escalation.
- Impact: one user can change another user profile or role if the handler accepts role fields.
- Recommended fix: require self-access or admin role, and block role changes for normal users.
Using "auth-analyzer". Assess a JWT middleware that decodes token payloads without signature verification.
Expected outcome:
- Critical finding: unsigned token payloads can be forged by attackers.
- Impact: attackers can impersonate users or admins.
- Recommended fix: verify signatures with allowed algorithms, issuer, audience, and short expiration.
Security Audit
SafeThe static findings are triggered by Markdown examples inside a defensive authentication security guide, not by executable skill code. The weak crypto, curl, fetch, process.env, and token snippets are presented as teaching examples or remediation examples, so no malicious execution, exfiltration, or prompt injection evidence was found.
Risk Factors
โ๏ธ External commands (50)
๐ Network access (8)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/curiouslearner-auth-analyzer/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/curiouslearner-auth-analyzer?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/curiouslearner-auth-analyzer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/curiouslearner-auth-analyzer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/curiouslearner-auth-analyzer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
CuriousLearner. (2026). auth-analyzer security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/curiouslearner-auth-analyzer/audits/10BibTeX citation
@techreport{curiouslearner-curiouslearner-auth-analyzer-2026,
author = {CuriousLearner},
title = {auth-analyzer security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/curiouslearner-auth-analyzer/audits/10},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "auth-analyzer security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
- name: "CuriousLearner"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/curiouslearner-auth-analyzer/audits/10"
identifiers:
- type: other
value: "skillstore:curiouslearner-auth-analyzer:audit:10"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Review a login implementation
Check password hashing, rate limits, session regeneration, and account enumeration defenses before release.
Audit access control rules
Find missing ownership checks, overbroad roles, and authorization gaps across protected routes.
Prepare a remediation report
Turn auth findings into prioritized fixes with clear impact, severity, and compliance context.
Try These Prompts
Use auth-analyzer to review this authentication file. Focus on password handling, session setup, and obvious login risks.
Use auth-analyzer to review our JWT and OAuth flow. Check token signing, verification, expiration, issuer, audience, state, and PKCE handling.
Use auth-analyzer to audit these protected routes. Identify missing ownership checks, role bypasses, IDOR risks, and privilege escalation paths.
Use auth-analyzer to produce a prioritized authentication and authorization security report. Include severity, affected flow, exploit impact, and concrete remediation steps.
Best Practices
- Provide the full authentication flow, including middleware, routes, models, and configuration.
- Ask for prioritized findings with impact and concrete remediation steps.
- Validate authorization findings against real business ownership and role rules.
Avoid
- Do not use this skill to test live systems without explicit authorization.
- Do not review only frontend role checks when backend authorization determines security.
- Do not treat example code as production evidence without confirming where it runs.
Frequently Asked Questions
What does this skill review?
Can it replace a penetration test?
Does it support Claude Code?
What input should I provide?
Will it find business logic issues?
Is it safe for sensitive code?
Developer Details
Author
CuriousLearnerLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
7db9b9f06e0ab79c575b58bc48c4d8dc9849f424
Maintenance freshness
7/18/2026
Usage
6 downloads ยท 267 views
File structure
๐ SKILL.md