Oauth Security Anti Pattern
CheckedHelps with OAuth, 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 igbuend/grimbard --skill oauth-security-anti-pattern -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
igbuend
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 igbuend/grimbard at cde088f5d7.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- cde088f5d7
- Scanned
- 1 file, 124 lines
About this skill
What it does
This skill identifies and explains common OAuth security anti-patterns. It helps users understand vulnerabilities that arise from misconfigured or improperly implemented OAuth flows, such as exposed client secrets, improper redirect URI validation, and insufficient scope enforcement. The skill provides explanations of these patterns and suggests remediation strategies to improve overall application security.
When to use it
- Security Audits: During code reviews or penetration testing to identify potential OAuth vulnerabilities.
- Design Reviews: To ensure secure OAuth integration during the design phase of new applications.
- Incident Response: To analyze security incidents involving OAuth and determine root causes.
- Developer Training: As a learning tool for developers unfamiliar with OAuth best practices.
Key capabilities
- Identification of common OAuth anti-patterns.
- Explanation of the risks associated with each anti-pattern.
- Recommendations for remediation strategies.
Example prompts
- "What are some common OAuth security vulnerabilities?"
- "Explain the risk of exposed client secrets in an OAuth flow."
- "How can I prevent redirect URI manipulation attacks in my application?"
Tips & gotchas
This skill assumes a basic understanding of OAuth concepts. It's most effective when used to review existing implementations or designs, rather than as a standalone guide for building OAuth integrations from scratch.