Scanning Api Security
CheckedHelps with API, 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 jeremylongshore/tons-of-skills-marketplace --skill scanning-api-security -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
jeremylongshore
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 jeremylongshore/claude-code-plugins-plus-skills at a7be181f58.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- a7be181f58
- Scanned
- 4 files, 358 lines
About this skill
What it does
This skill automates the process of scanning APIs for security vulnerabilities. It identifies common issues like SQL injection, cross-site scripting (XSS), and insecure direct object references. The tool provides detailed reports outlining potential risks and recommendations for remediation, helping to improve overall API security posture.
When to use it
- Security Audits: Regularly scan your APIs as part of a broader security audit process.
- New API Development: Integrate scanning into the development lifecycle to identify vulnerabilities early on.
- Post-Deployment Checks: Perform scans after deploying new versions or making significant changes to an existing API.
- Vulnerability Assessments: Quickly assess the security posture of third-party APIs before integration.
Key capabilities
- Automated vulnerability scanning
- Identification of SQL injection vulnerabilities
- Detection of Cross-Site Scripting (XSS) risks
- Reporting on insecure direct object references
- Detailed remediation recommendations
Example prompts
- "Scan the API at
https://example.com/apifor common security vulnerabilities." - "Perform a comprehensive scan of our internal payment processing API and generate a report."
- "Analyze the
/usersendpoint onhttps://my-app.iofor XSS risks."
Tips & gotchas
The skill requires proper authorization to access and test the target APIs. Ensure you have the necessary permissions before initiating scans, as unauthorized testing can be illegal or violate terms of service.