Skip to content
TrustedSkillsbeta
Back to all skills

Security Visual Testing

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

Helps with security, testing 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-visual-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-visual-testing/SKILL.md
Scanned
8 files, 1,846 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 enables AI agents to perform security-aware visual testing of web pages. It leverages the qe-browser toolchain and the Vibium engine for browser automation, incorporating checks for prompt injection vulnerabilities before screenshots are stored and performing typed assertions including detection of data-leak requests. The goal is to identify and mitigate potential security risks while ensuring visual consistency across different viewports.

When to use it

  • Testing login pages: These pages often contain sensitive information like passwords and emails that require careful handling.
  • Running a visual regression suite: This skill facilitates parallel viewport testing and baseline comparison for detecting visual regressions.
  • Testing payment forms: Payment forms frequently involve credit card data, necessitating masking of sensitive information before screenshots are saved.
  • Auditing public marketing pages: Use when there's a possibility of sensitive data being displayed on publicly accessible web pages.
  • Not suitable for API-only testing: For security testing of APIs, use the dedicated "security-testing" skill instead.

Key capabilities

  • URL Validation: Blocks malicious URLs before navigation by preventing javascript:, data:, and file: schemes.
  • PII Detection: Identifies and flags over six types of sensitive Personally Identifiable Information (PII).
  • Parallel Viewports: Tests web pages across four different viewport sizes simultaneously for faster testing.
  • Visual Regression: Performs pixel-by-pixel comparisons with a configurable threshold to detect visual changes.
  • Accessibility Audit: Evaluates compliance with WCAG 2.1 accessibility guidelines (A/AA/AAA).
  • Prompt Injection Scanning: Scans page content for prompt injection patterns before screenshots are stored using check-injection.js.

Example prompts

  • "Run a security visual audit on https://example.com, including accessibility checks."
  • "Perform visual regression testing with baseline comparison for the login page."
  • "Test the payment form and ensure credit card data is masked before taking screenshots."

Tips & gotchas

  • PII Masking: Always mask PII (like emails, phone numbers, or credit card details) before storing any screenshots.
  • Viewport Coverage: Ensure testing covers all target viewports to catch visual issues across different devices.
  • Baseline Management: Store baselines in version control for reliable regression testing.