Skip to content
TrustedSkillsbeta
Back to all skills

Security Testing

Checked
proffesor-for-testing·vlatest·security·MIT

Helps with testing, security as part of implementing security and authentication workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add proffesor-for-testing/agentic-qe --skill security-testing -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

proffesor-for-testing

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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 proffesor-for-testing/agentic-qe at 124d8c735e.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
124d8c735e
Manifest
assets/skills/security-testing/SKILL.md
Scanned
18 files, 4,570 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill empowers AI agents to execute comprehensive security testing workflows, including vulnerability scanning and penetration simulation. It automates the identification of potential threats across web applications and infrastructure to ensure robust defense mechanisms.

When to use it

  • Automating routine security audits for CI/CD pipelines before deployment.
  • Simulating attacker behaviors to identify exploitable vulnerabilities in production-like environments.
  • Generating detailed security reports with actionable remediation steps for development teams.
  • Validating the effectiveness of existing firewalls and intrusion detection systems.

Key capabilities

  • Automated vulnerability scanning across multiple protocols (HTTP, HTTPS, SSH).
  • Penetration testing simulation to uncover logical flaws and misconfigurations.
  • Real-time threat detection and risk assessment scoring.
  • Integration with popular security frameworks like OWASP Top 10.
  • Customizable test scopes based on specific application requirements.

Example prompts

  • "Run a full security audit on our staging environment using the OWASP methodology."
  • "Simulate a SQL injection attack on our login form and report any findings."
  • "Scan this API endpoint for authentication bypass vulnerabilities and provide a risk score."

Tips & gotchas

Ensure you have explicit permission to test target systems, as unauthorized scanning may violate legal agreements. Always run tests in isolated or staging environments to prevent accidental disruption of live services.