Auth Security Reviewer
CheckedHelps with authentication, security as part of implementing security and authentication workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add patricio0312rev/skills --skill auth-security-reviewer -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
patricio0312rev
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned patricio0312rev/skills at 79ea6af485.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 79ea6af485
- Scanned
- 1 file, 411 lines
About this skill
What it does
The Auth Security Reviewer skill helps identify and correct common security vulnerabilities in authentication workflows, including session management, JSON Web Token (JWT) implementation, and Cross-Site Request Forgery (CSRF) protection. It provides examples of insecure configurations alongside secure alternatives, highlighting best practices for protecting user data and preventing unauthorized access. The skill focuses on code review to improve the overall security posture of applications handling authentication.
When to use it
- When implementing or reviewing authentication systems in a web application.
- To identify potential vulnerabilities related to session management and JWT usage.
- For ensuring proper CSRF protection is implemented across state-changing routes.
- During code audits to improve the security of existing authentication flows.
Key capabilities
- Session Security Review: Identifies insecure session configurations (e.g., weak secrets, unnecessary
resaveandsaveUninitialized, missing HTTPS-only cookie flags) and provides secure alternatives. - JWT Security Review: Highlights vulnerabilities in JWT implementations (e.g., hardcoded secrets, lack of expiration, storing tokens in localStorage) and suggests secure practices like using environment variables for secrets, setting short expiry times, and storing tokens in HTTPOnly cookies.
- CSRF Protection: Demonstrates the use of
csurfmiddleware to protect against CSRF attacks and provides examples of how to integrate it into routes and provide CSRF tokens to the frontend.
Example prompts
- "Review this session configuration code for security vulnerabilities." (followed by pasting the insecure session configuration)
- "How can I securely implement JWT authentication in my application?"
- "Show me an example of how to protect a POST route from CSRF attacks."
Tips & gotchas
- The skill provides specific examples using libraries like
jsonwebtokenandcsurf. Ensure these dependencies are available in your environment. - The provided code snippets are illustrative; adapt them to fit your application's specific needs and security policies.
- Pay close attention to the recommendations regarding storing secrets (using environment variables) and token expiry times for maximum security.